Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9e1049a0c40998f52133d8890f5aa4e82291150bb961962b37b5c2b2c36c1ff

Tx prefix hash: 8f17dfd494295ac8645d63d64d35f1a1c5c41028c014c3257c4aa860aff9b1dc
Tx public key: fee0dbe9ba115c4967b33375c0adf93dc9d3305a9b6b6453aa1a67cea19b3ee2
Timestamp: 1627882762 Timestamp [UCT]: 2021-08-02 05:39:22 Age [y:d:h:m:s]: 03:122:03:47:35
Block: 305669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859944 RingCT/type: yes/0
Extra: 01fee0dbe9ba115c4967b33375c0adf93dc9d3305a9b6b6453aa1a67cea19b3ee202110000000c01f1e57f000000000000000000

1 output(s) for total of 59.593611068000 dcy

stealth address amount amount idx
00: 78e3bd5526d985e61bbbfaa4f4ac92e2158db5ea571d115bf2707dfa5ec508d5 59.593611068000 637550 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": 305679, "vin": [ { "gen": { "height": 305669 } } ], "vout": [ { "amount": 59593611068, "target": { "key": "78e3bd5526d985e61bbbfaa4f4ac92e2158db5ea571d115bf2707dfa5ec508d5" } } ], "extra": [ 1, 254, 224, 219, 233, 186, 17, 92, 73, 103, 179, 51, 117, 192, 173, 249, 61, 201, 211, 48, 90, 155, 107, 100, 83, 170, 26, 103, 206, 161, 155, 62, 226, 2, 17, 0, 0, 0, 12, 1, 241, 229, 127, 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