Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4d1d314b39d3b2ccb1978359e5188a697b0592479d63eb3dbaa5af51ad271fe

Tx prefix hash: 5b1ea49ad47821ac697d4a2c4418b304937cb7592461e4edfab7884b414471dc
Tx public key: 0446ab3351f6be473acf61f5ca0586ff0495e51082a0fe9d8cdf4b43dbb0e3e5
Timestamp: 1713988750 Timestamp [UCT]: 2024-04-24 19:59:10 Age [y:d:h:m:s]: 00:345:16:32:31
Block: 1007716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247131 RingCT/type: yes/0
Extra: 010446ab3351f6be473acf61f5ca0586ff0495e51082a0fe9d8cdf4b43dbb0e3e502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02e4d2e334b3376b07baaac279eca7e96dbfdd4e10e5a572a90b1bc40725c611 0.600000000000 1469148 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": 1007726, "vin": [ { "gen": { "height": 1007716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02e4d2e334b3376b07baaac279eca7e96dbfdd4e10e5a572a90b1bc40725c611" } } ], "extra": [ 1, 4, 70, 171, 51, 81, 246, 190, 71, 58, 207, 97, 245, 202, 5, 134, 255, 4, 149, 229, 16, 130, 160, 254, 157, 140, 223, 75, 67, 219, 176, 227, 229, 2, 17, 0, 0, 0, 5, 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