Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5cf66b309bdf33f06429273cc963b9ca15affdbb2cf5ee33ca8f22fc3e11114

Tx prefix hash: e31011ad166730f09e1217c2d5f0ff86a7a4f9534eb30891919c9c03e2a964f4
Tx public key: 6dc97a3ffb25fdd20fa091c781b8f433c67151d7bad70cb4f147c231e8a41004
Timestamp: 1736352959 Timestamp [UCT]: 2025-01-08 16:15:59 Age [y:d:h:m:s]: 00:314:21:52:34
Block: 1192990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222580 RingCT/type: yes/0
Extra: 016dc97a3ffb25fdd20fa091c781b8f433c67151d7bad70cb4f147c231e8a410040211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0867479b999d7b7a2560b1bc31b88ce43d3d6dc0f8501235aff4099a06208cd4 0.600000000000 1679547 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": 1193000, "vin": [ { "gen": { "height": 1192990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0867479b999d7b7a2560b1bc31b88ce43d3d6dc0f8501235aff4099a06208cd4" } } ], "extra": [ 1, 109, 201, 122, 63, 251, 37, 253, 210, 15, 160, 145, 199, 129, 184, 244, 51, 198, 113, 81, 215, 186, 215, 12, 180, 241, 71, 194, 49, 232, 164, 16, 4, 2, 17, 0, 0, 0, 1, 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