Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e854276250c8efcb5e0b50a3452b1507bd6ed58eaa09f91f3aa615ba6bc3c78e

Tx prefix hash: aed2e6e8215ae40463d3fed396a3733598cc0af3c9550c8f893d1bfef00d68ca
Tx public key: 5820e68add9a8789a23195ad02c4a766114dba424efe3c0a98d76a0ecd5336b7
Timestamp: 1720687684 Timestamp [UCT]: 2024-07-11 08:48:04 Age [y:d:h:m:s]: 00:294:18:48:55
Block: 1063266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210622 RingCT/type: yes/0
Extra: 015820e68add9a8789a23195ad02c4a766114dba424efe3c0a98d76a0ecd5336b702110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f4b0108fc18532fac67bba9194ea0fa3a1b5c3acd66394b7387c5da9e9d06cd 0.600000000000 1533781 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": 1063276, "vin": [ { "gen": { "height": 1063266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f4b0108fc18532fac67bba9194ea0fa3a1b5c3acd66394b7387c5da9e9d06cd" } } ], "extra": [ 1, 88, 32, 230, 138, 221, 154, 135, 137, 162, 49, 149, 173, 2, 196, 167, 102, 17, 77, 186, 66, 78, 254, 60, 10, 152, 215, 106, 14, 205, 83, 54, 183, 2, 17, 0, 0, 0, 12, 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