Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e35b7db370566c895dbb377d78ff9dd3d736434a8d54cdfe529183e16a3cccec

Tx prefix hash: aa272e6fedea491852618730b55ff6250f1741e31b6e6d3bae91d9ad779202b4
Tx public key: 5ebc52d4a01478f7323b73e5d0bb0df35830e0255b1c8f2270c6b21ad2a7561f
Timestamp: 1724076090 Timestamp [UCT]: 2024-08-19 14:01:30 Age [y:d:h:m:s]: 00:268:23:38:44
Block: 1091350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192149 RingCT/type: yes/0
Extra: 015ebc52d4a01478f7323b73e5d0bb0df35830e0255b1c8f2270c6b21ad2a7561f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a63f34d0510f6335284e8758e69613d9c77fe68a23e5eb6e026ea55152bec18d 0.600000000000 1565981 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1091360, "vin": [ { "gen": { "height": 1091350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a63f34d0510f6335284e8758e69613d9c77fe68a23e5eb6e026ea55152bec18d" } } ], "extra": [ 1, 94, 188, 82, 212, 160, 20, 120, 247, 50, 59, 115, 229, 208, 187, 13, 243, 88, 48, 224, 37, 91, 28, 143, 34, 112, 198, 178, 26, 210, 167, 86, 31, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8