Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464a0608dcdf3bee7bc125054f93026d044d736321b0f4717630d37c5be2b46a

Tx prefix hash: 852f8fcad1db81602750a9d6d05d95ea0d18cb08b7c9308ad9e897795199b79f
Tx public key: 812380bada61519df2bd874f1c27d9dcb0ca79fd57d6db0c1d1cd9c36e1ce0cb
Timestamp: 1709467833 Timestamp [UCT]: 2024-03-03 12:10:33 Age [y:d:h:m:s]: 01:056:02:20:55
Block: 970252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301111 RingCT/type: yes/0
Extra: 01812380bada61519df2bd874f1c27d9dcb0ca79fd57d6db0c1d1cd9c36e1ce0cb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 702fd2d596754971b244d26d8a939f3cae9620297a8f977fb7fdd510ff411af6 0.600000000000 1430103 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": 970262, "vin": [ { "gen": { "height": 970252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "702fd2d596754971b244d26d8a939f3cae9620297a8f977fb7fdd510ff411af6" } } ], "extra": [ 1, 129, 35, 128, 186, 218, 97, 81, 157, 242, 189, 135, 79, 28, 39, 217, 220, 176, 202, 121, 253, 87, 214, 219, 12, 29, 28, 217, 195, 110, 28, 224, 203, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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