Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09971eb00db84cbf5f23eaf4bbb1db9522f68b0a957722e49af61f1964483e0c

Tx prefix hash: ea22e3d873e6490a6b930a7c93693d62be62c693d61d7fef8f72e25738ca9914
Tx public key: c9fa17b824cbc47f602a71eaf9efd4e3a0e4069f7ce30001317bcbbcf67f7e3b
Timestamp: 1749137906 Timestamp [UCT]: 2025-06-05 15:38:26 Age [y:d:h:m:s]: 00:161:21:00:07
Block: 1298582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113369 RingCT/type: yes/0
Extra: 01c9fa17b824cbc47f602a71eaf9efd4e3a0e4069f7ce30001317bcbbcf67f7e3b02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71a95238874edb69a91e22b67f02c0133bf17c8bc32ce5922f579caf7cc9d87c 0.600000000000 1786111 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": 1298592, "vin": [ { "gen": { "height": 1298582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71a95238874edb69a91e22b67f02c0133bf17c8bc32ce5922f579caf7cc9d87c" } } ], "extra": [ 1, 201, 250, 23, 184, 36, 203, 196, 127, 96, 42, 113, 234, 249, 239, 212, 227, 160, 228, 6, 159, 124, 227, 0, 1, 49, 123, 203, 188, 246, 127, 126, 59, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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