Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6c7d7806139e44ad918d7e1d608b8ed5aeefdc0f9ac8f4e16905f97cb273c04

Tx prefix hash: 3ca4c4b3316d8409891e9e913e53900ec022097bfdc56cf1b8154b7cfdcb71f1
Tx public key: ceb5e3900581f0af5f8751d9318c8a8c14aa7cfaad9a0360d7d8b1c14f072d08
Timestamp: 1710663141 Timestamp [UCT]: 2024-03-17 08:12:21 Age [y:d:h:m:s]: 01:072:13:48:59
Block: 980172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312869 RingCT/type: yes/0
Extra: 01ceb5e3900581f0af5f8751d9318c8a8c14aa7cfaad9a0360d7d8b1c14f072d080211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 010e7e19d34a052b61463ff8aa933f22cea96b4d44154057c9669cf1bd98da82 0.600000000000 1440231 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": 980182, "vin": [ { "gen": { "height": 980172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "010e7e19d34a052b61463ff8aa933f22cea96b4d44154057c9669cf1bd98da82" } } ], "extra": [ 1, 206, 181, 227, 144, 5, 129, 240, 175, 95, 135, 81, 217, 49, 140, 138, 140, 20, 170, 124, 250, 173, 154, 3, 96, 215, 216, 177, 193, 79, 7, 45, 8, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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