Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef228fcf88b9afa36a7383558a16ba808bde6d0de100eef803c69dd41cda8ad9

Tx prefix hash: bf8a0b24ff1ce4b8de37b5520c2613e9c6e832408997dd0fb62aa2487b607da1
Tx public key: d3cbf905cab76dd6d35077e05c3d5928a9d4ce5cfbe53889e57a5117970611f0
Timestamp: 1694012100 Timestamp [UCT]: 2023-09-06 14:55:00 Age [y:d:h:m:s]: 01:210:13:37:23
Block: 842286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411595 RingCT/type: yes/0
Extra: 01d3cbf905cab76dd6d35077e05c3d5928a9d4ce5cfbe53889e57a5117970611f0021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.993474903000 dcy

stealth address amount amount idx
00: 4096d36a3533e33445afbeefc3003fdec8897b250236964e1c22abd1055cd8c6 0.993474903000 1295396 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": 842296, "vin": [ { "gen": { "height": 842286 } } ], "vout": [ { "amount": 993474903, "target": { "key": "4096d36a3533e33445afbeefc3003fdec8897b250236964e1c22abd1055cd8c6" } } ], "extra": [ 1, 211, 203, 249, 5, 202, 183, 109, 214, 211, 80, 119, 224, 92, 61, 89, 40, 169, 212, 206, 92, 251, 229, 56, 137, 229, 122, 81, 23, 151, 6, 17, 240, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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