Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab09e23ef8f821345e870013ab8bb449a02c68ed69c42a96bd255c51a347506

Tx prefix hash: 1ebeb55fcf6353045fd946c1fc5da336a41937a8f921768119a9e33a7a7b2c73
Tx public key: f3a364c03ae463abc23e973234cb2bd0eee55fb9ec588d814ec66c36d1bc8ef1
Timestamp: 1725065390 Timestamp [UCT]: 2024-08-31 00:49:50 Age [y:d:h:m:s]: 00:227:14:12:04
Block: 1099549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162510 RingCT/type: yes/0
Extra: 01f3a364c03ae463abc23e973234cb2bd0eee55fb9ec588d814ec66c36d1bc8ef1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34453a052992aace215b1ad8cbd7c00057a3812efbfc26900f4efb297535480e 0.600000000000 1575512 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": 1099559, "vin": [ { "gen": { "height": 1099549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34453a052992aace215b1ad8cbd7c00057a3812efbfc26900f4efb297535480e" } } ], "extra": [ 1, 243, 163, 100, 192, 58, 228, 99, 171, 194, 62, 151, 50, 52, 203, 43, 208, 238, 229, 95, 185, 236, 88, 141, 129, 78, 198, 108, 54, 209, 188, 142, 241, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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