Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f01fa0514936388006527208a5b18f4c38dcedfe55746d8f6e0876cd5bbb564

Tx prefix hash: f24af0e3293dc364f2c06cce49230085ddb1d3b12da2bfad183ccc051adaf161
Tx public key: e31d8d8f1e3a1ffb2b59df9b339f38a86488ccbc899b39d50012d48df0d7910a
Timestamp: 1736893342 Timestamp [UCT]: 2025-01-14 22:22:22 Age [y:d:h:m:s]: 00:061:12:52:14
Block: 1197463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43773 RingCT/type: yes/0
Extra: 01e31d8d8f1e3a1ffb2b59df9b339f38a86488ccbc899b39d50012d48df0d7910a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e594f786f4935a9d6e80878ee3d4c35e6e705a34fbff4534103ac1fa2ab9af21 0.600000000000 1684070 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": 1197473, "vin": [ { "gen": { "height": 1197463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e594f786f4935a9d6e80878ee3d4c35e6e705a34fbff4534103ac1fa2ab9af21" } } ], "extra": [ 1, 227, 29, 141, 143, 30, 58, 31, 251, 43, 89, 223, 155, 51, 159, 56, 168, 100, 136, 204, 188, 137, 155, 57, 213, 0, 18, 212, 141, 240, 215, 145, 10, 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