Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b1d6b22210d605203e50c4663045e1eb57f137f3b86b0127cc9e7b6d710aac

Tx prefix hash: 4a42d49caaff531ac31c633b0b3bbc00330851a2658a4dba355aa8a6018119b6
Tx public key: 56aa247dc4bd24c909774300b8e96ce9454e7a11e7ef2ac87706fb3fbefe85f5
Timestamp: 1760515189 Timestamp [UCT]: 2025-10-15 07:59:49 Age [y:d:h:m:s]: 00:069:16:17:32
Block: 1390335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49880 RingCT/type: yes/0
Extra: 0156aa247dc4bd24c909774300b8e96ce9454e7a11e7ef2ac87706fb3fbefe85f50211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aed58f61c422f303a0b134d5c417d0e57b4d397def57bbeae982f1fc764bd370 0.600000000000 1878576 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": 1390345, "vin": [ { "gen": { "height": 1390335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aed58f61c422f303a0b134d5c417d0e57b4d397def57bbeae982f1fc764bd370" } } ], "extra": [ 1, 86, 170, 36, 125, 196, 189, 36, 201, 9, 119, 67, 0, 184, 233, 108, 233, 69, 78, 122, 17, 231, 239, 42, 200, 119, 6, 251, 63, 190, 254, 133, 245, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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