Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9c46ea0e8cd0cfe31ba1649920e4932190065b53c7dd0e626b3bafc580d933

Tx prefix hash: df306083ad4e647afd042f6c0155124f8fb80dfe173e32772ffcfe480cb3cec9
Tx public key: fecad000ea092e54fd4c16f59401ab318c9e75414d19724a9d177ca510d6e86a
Timestamp: 1649487317 Timestamp [UCT]: 2022-04-09 06:55:17 Age [y:d:h:m:s]: 02:268:01:40:35
Block: 476384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 711371 RingCT/type: yes/0
Extra: 01fecad000ea092e54fd4c16f59401ab318c9e75414d19724a9d177ca510d6e86a02110000000337cb3088000000000000000000

1 output(s) for total of 16.201017521000 dcy

stealth address amount amount idx
00: 659219bf349f5082080b8e173cc0d3a819a3802c4c667626ff9389ac44eec8dc 16.201017521000 896843 of 0

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": 476394, "vin": [ { "gen": { "height": 476384 } } ], "vout": [ { "amount": 16201017521, "target": { "key": "659219bf349f5082080b8e173cc0d3a819a3802c4c667626ff9389ac44eec8dc" } } ], "extra": [ 1, 254, 202, 208, 0, 234, 9, 46, 84, 253, 76, 22, 245, 148, 1, 171, 49, 140, 158, 117, 65, 77, 25, 114, 74, 157, 23, 124, 165, 16, 214, 232, 106, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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