Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45bd72bf96889a75ffb24efc2de50263ebad74ea8afc36d3dce0aad6cf345b17

Tx prefix hash: 285f6c6213b94b94be79fe36c7efa90b976c5036ad2e4c26ae4ea874cda1db28
Tx public key: e10d07a4aa79c8e6499faf2b26778ecc435df4153e9d1405761f925762ca6e67
Timestamp: 1699384194 Timestamp [UCT]: 2023-11-07 19:09:54 Age [y:d:h:m:s]: 01:187:19:57:56
Block: 886645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395454 RingCT/type: yes/0
Extra: 01e10d07a4aa79c8e6499faf2b26778ecc435df4153e9d1405761f925762ca6e6702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.708234460000 dcy

stealth address amount amount idx
00: 6f6112d463e62c4a3a6d0b749792347e26f4b7fc9d6b80f41866b7c2e0d6b1e3 0.708234460000 1342474 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": 886655, "vin": [ { "gen": { "height": 886645 } } ], "vout": [ { "amount": 708234460, "target": { "key": "6f6112d463e62c4a3a6d0b749792347e26f4b7fc9d6b80f41866b7c2e0d6b1e3" } } ], "extra": [ 1, 225, 13, 7, 164, 170, 121, 200, 230, 73, 159, 175, 43, 38, 119, 142, 204, 67, 93, 244, 21, 62, 157, 20, 5, 118, 31, 146, 87, 98, 202, 110, 103, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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