Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2609dc7a6fe865617827698ba564728196d9e161cced4a8223692805ca65710

Tx prefix hash: cce2dfcbde9d2c9dd912c3676d808ff98f7c60a3b6dabe9dec3a240d543344cb
Tx public key: 888490b528eae09aaf9f0c6368d1f29bbb9ce0e40a3c96e917be2c7f78972ba8
Timestamp: 1721843821 Timestamp [UCT]: 2024-07-24 17:57:01 Age [y:d:h:m:s]: 00:287:12:12:06
Block: 1072830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205424 RingCT/type: yes/0
Extra: 01888490b528eae09aaf9f0c6368d1f29bbb9ce0e40a3c96e917be2c7f78972ba802110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851f280dc8cc6cf71b41487be87745acd1415965d3bd304ca056d0c3d5a1005c 0.600000000000 1545327 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": 1072840, "vin": [ { "gen": { "height": 1072830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851f280dc8cc6cf71b41487be87745acd1415965d3bd304ca056d0c3d5a1005c" } } ], "extra": [ 1, 136, 132, 144, 181, 40, 234, 224, 154, 175, 159, 12, 99, 104, 209, 242, 155, 187, 156, 224, 228, 10, 60, 150, 233, 23, 190, 44, 127, 120, 151, 43, 168, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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