Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a1f26b0dbf8e00403d84839313ab355844efd54ff1a56337d0109595567b4fe

Tx prefix hash: 51aa4e7b9439e824a5f33a4db63a9691390218f76eef699f3b41398302c567ee
Tx public key: c0bd6d26d87f5e286f1bb26cb515213ffd7e90e6c608e8dc37da37e55bcc43c9
Timestamp: 1761323711 Timestamp [UCT]: 2025-10-24 16:35:11 Age [y:d:h:m:s]: 00:022:03:05:07
Block: 1397050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15819 RingCT/type: yes/0
Extra: 01c0bd6d26d87f5e286f1bb26cb515213ffd7e90e6c608e8dc37da37e55bcc43c90211000000095dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb8d7407c991177555516c8933030956a3fa8a43ca5221a8031b4353f58e50ab 0.600000000000 1885341 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": 1397060, "vin": [ { "gen": { "height": 1397050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb8d7407c991177555516c8933030956a3fa8a43ca5221a8031b4353f58e50ab" } } ], "extra": [ 1, 192, 189, 109, 38, 216, 127, 94, 40, 111, 27, 178, 108, 181, 21, 33, 63, 253, 126, 144, 230, 198, 8, 232, 220, 55, 218, 55, 229, 91, 204, 67, 201, 2, 17, 0, 0, 0, 9, 93, 251, 190, 42, 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