Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d2ed28023f0d4e56bb276b413ba62375294814a9bdcb21c3a61ff1b1e3e5cb

Tx prefix hash: 8606885db4440cceb762c647fa9aa93248e916c1748ed7dc583ce44dc10c53b0
Tx public key: f9e3875f4e1d90e3ed7e434f0a4b549423619763f23ce75bcb6629c08fb96264
Timestamp: 1725988326 Timestamp [UCT]: 2024-09-10 17:12:06 Age [y:d:h:m:s]: 00:120:12:15:56
Block: 1107204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86187 RingCT/type: yes/0
Extra: 01f9e3875f4e1d90e3ed7e434f0a4b549423619763f23ce75bcb6629c08fb9626402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 658e69647a77e5d4e4044143539c563d4b0c4b3d456e42e92225ebeb57e2dd37 0.600000000000 1584811 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": 1107214, "vin": [ { "gen": { "height": 1107204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "658e69647a77e5d4e4044143539c563d4b0c4b3d456e42e92225ebeb57e2dd37" } } ], "extra": [ 1, 249, 227, 135, 95, 78, 29, 144, 227, 237, 126, 67, 79, 10, 75, 84, 148, 35, 97, 151, 99, 242, 60, 231, 91, 203, 102, 41, 192, 143, 185, 98, 100, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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