Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3666de6b019912ad1f0b021a8e4a9614c7b0014e9a88a8036517144ec5ecede2

Tx prefix hash: 82d2d0356907af9f8b4fda5a8ed69b90ae1736de45d3e00bab50772de1bf1b81
Tx public key: 75d0b859e6e4e9689a35e69b43a3036dc9c1fb96f6e7fb3bb968fae513d81a92
Timestamp: 1736957127 Timestamp [UCT]: 2025-01-15 16:05:27 Age [y:d:h:m:s]: 00:153:18:27:09
Block: 1197984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109605 RingCT/type: yes/0
Extra: 0175d0b859e6e4e9689a35e69b43a3036dc9c1fb96f6e7fb3bb968fae513d81a920211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8eef4e36aa83f947a673d097a85ed18865812d1c3af3f531b0aa790c0edf73 0.600000000000 1684601 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": 1197994, "vin": [ { "gen": { "height": 1197984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8eef4e36aa83f947a673d097a85ed18865812d1c3af3f531b0aa790c0edf73" } } ], "extra": [ 1, 117, 208, 184, 89, 230, 228, 233, 104, 154, 53, 230, 155, 67, 163, 3, 109, 201, 193, 251, 150, 246, 231, 251, 59, 185, 104, 250, 229, 19, 216, 26, 146, 2, 17, 0, 0, 0, 8, 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