Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6507ebfbbd895e9913b88ad8168117b761428d1670e993c38e2daa616f5c67f2

Tx prefix hash: a6079688a7c7ebdd53cf71a2ea98859ebac9cb9edcdc044801df0c88191fa298
Tx public key: 373e5f54143ccc7cd37ded3fc4dc28f5f9f0e30f4ca4b9be73c14cf373ba3a70
Timestamp: 1760038599 Timestamp [UCT]: 2025-10-09 19:36:39 Age [y:d:h:m:s]: 00:091:21:47:07
Block: 1386365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65827 RingCT/type: yes/0
Extra: 01373e5f54143ccc7cd37ded3fc4dc28f5f9f0e30f4ca4b9be73c14cf373ba3a7002110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3981ca679cbc988538a132f2f25ccb77e7ff8b34258d4d371ac527b23cb4a360 0.600000000000 1874530 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": 1386375, "vin": [ { "gen": { "height": 1386365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3981ca679cbc988538a132f2f25ccb77e7ff8b34258d4d371ac527b23cb4a360" } } ], "extra": [ 1, 55, 62, 95, 84, 20, 60, 204, 124, 211, 125, 237, 63, 196, 220, 40, 245, 249, 240, 227, 15, 76, 164, 185, 190, 115, 193, 76, 243, 115, 186, 58, 112, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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