Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d613e6c333c30fe911ba2600c43af1a207e7a42932d9d07aa323c3d26fcc5df9

Tx prefix hash: 82a20238910d7ab46965cc71c681a24a7e996293ffcb0cd5b8f4465649992daf
Tx public key: 01e19fd2d1ad81c357bccecfd36141aedd83c8e5716ee8f003d2d45f0a30a352
Timestamp: 1733032045 Timestamp [UCT]: 2024-12-01 05:47:25 Age [y:d:h:m:s]: 00:117:18:28:46
Block: 1165501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83972 RingCT/type: yes/0
Extra: 0101e19fd2d1ad81c357bccecfd36141aedd83c8e5716ee8f003d2d45f0a30a3520211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 144a77160fee677c4ea165b544815b9e88ce458dfee69cb10973cb8943f57701 0.600000000000 1651176 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": 1165511, "vin": [ { "gen": { "height": 1165501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "144a77160fee677c4ea165b544815b9e88ce458dfee69cb10973cb8943f57701" } } ], "extra": [ 1, 1, 225, 159, 210, 209, 173, 129, 195, 87, 188, 206, 207, 211, 97, 65, 174, 221, 131, 200, 229, 113, 110, 232, 240, 3, 210, 212, 95, 10, 48, 163, 82, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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