Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b00b39d82c63c570fc55e103ee6d1df96ca01bc4f1635db0d82f28dd26a263

Tx prefix hash: fdcd1398377805dba369be070510966bd0c8dced5a3ad177457892cc3ca020e2
Tx public key: 037afd7534d5ed3c5764e86827b6137b6dc98430fa0d0b89ea5416bedd7dd33d
Timestamp: 1736724674 Timestamp [UCT]: 2025-01-12 23:31:14 Age [y:d:h:m:s]: 00:157:03:59:29
Block: 1196067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112012 RingCT/type: yes/0
Extra: 01037afd7534d5ed3c5764e86827b6137b6dc98430fa0d0b89ea5416bedd7dd33d0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ac1f47a1faa2b59170e3e551be4875ecbbfb7e5f0281e97a49b3acfbdd997b3 0.600000000000 1682664 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": 1196077, "vin": [ { "gen": { "height": 1196067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ac1f47a1faa2b59170e3e551be4875ecbbfb7e5f0281e97a49b3acfbdd997b3" } } ], "extra": [ 1, 3, 122, 253, 117, 52, 213, 237, 60, 87, 100, 232, 104, 39, 182, 19, 123, 109, 201, 132, 48, 250, 13, 11, 137, 234, 84, 22, 190, 221, 125, 211, 61, 2, 17, 0, 0, 0, 7, 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