Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc66335a9d3995b7d211955fa22e10109519a357a56411d01efa8eb79f38f709

Tx prefix hash: 94aad1b231a433322fca9a0828797faca716452ddb8c97b374f89833f88de63f
Tx public key: 73dfefba585aefc65a7537017c3cda24f2f2d1af6a20e532b57ec12ce3904849
Timestamp: 1710447613 Timestamp [UCT]: 2024-03-14 20:20:13 Age [y:d:h:m:s]: 01:239:17:43:16
Block: 978376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430038 RingCT/type: yes/0
Extra: 0173dfefba585aefc65a7537017c3cda24f2f2d1af6a20e532b57ec12ce390484902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d489339c3f3af934ef7de5aeb71e6e1c4e3f7a12aacc3302cd0f66a56b29fa9 0.600000000000 1438401 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": 978386, "vin": [ { "gen": { "height": 978376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d489339c3f3af934ef7de5aeb71e6e1c4e3f7a12aacc3302cd0f66a56b29fa9" } } ], "extra": [ 1, 115, 223, 239, 186, 88, 90, 239, 198, 90, 117, 55, 1, 124, 60, 218, 36, 242, 242, 209, 175, 106, 32, 229, 50, 181, 126, 193, 44, 227, 144, 72, 73, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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