Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bce9335d2438bc4f010142945a1e9817b645b510aca055cfc9c1ced286fc4cb

Tx prefix hash: 68f67c7d3850732f0ab8f0c26170bd29c40d346df3a21d69b49981ab33ce7366
Tx public key: a5f7f23bff75db34aa43f3d202bb628167d0ecc5a52a46a1e206b6f8d9894e15
Timestamp: 1733159289 Timestamp [UCT]: 2024-12-02 17:08:09 Age [y:d:h:m:s]: 00:119:17:37:11
Block: 1166555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85363 RingCT/type: yes/0
Extra: 01a5f7f23bff75db34aa43f3d202bb628167d0ecc5a52a46a1e206b6f8d9894e15021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b12e3ed7e2c13c105366d657666c5f305f30026032a16ce38c0414d668a2298 0.600000000000 1652242 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": 1166565, "vin": [ { "gen": { "height": 1166555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b12e3ed7e2c13c105366d657666c5f305f30026032a16ce38c0414d668a2298" } } ], "extra": [ 1, 165, 247, 242, 59, 255, 117, 219, 52, 170, 67, 243, 210, 2, 187, 98, 129, 103, 208, 236, 197, 165, 42, 70, 161, 226, 6, 182, 248, 217, 137, 78, 21, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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