Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2cf12625834a38b93370be81e9c45b6a14e1fc0ed25905b6e56d7f74a6ea002

Tx prefix hash: 80195510c7e4138f76e087ac81c5d31b78dca2e2cf66d1b8915bc1a2e0016f47
Tx public key: 1628ab1f00262685c656dcb0efbffbe69694092ac60b0e29ac01e65b71370a34
Timestamp: 1762942275 Timestamp [UCT]: 2025-11-12 10:11:15 Age [y:d:h:m:s]: 00:041:08:40:30
Block: 1410441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29603 RingCT/type: yes/0
Extra: 011628ab1f00262685c656dcb0efbffbe69694092ac60b0e29ac01e65b71370a34021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc95a79fcb2ebccfce7fd730874ef5ae74412d15fc764b621358fd3db9e5e4b0 0.600000000000 1898892 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": 1410451, "vin": [ { "gen": { "height": 1410441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc95a79fcb2ebccfce7fd730874ef5ae74412d15fc764b621358fd3db9e5e4b0" } } ], "extra": [ 1, 22, 40, 171, 31, 0, 38, 38, 133, 198, 86, 220, 176, 239, 191, 251, 230, 150, 148, 9, 42, 198, 11, 14, 41, 172, 1, 230, 91, 113, 55, 10, 52, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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