Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e786e0a924e904386299efc511545993df923e6b6140e4ad9cbfc9fbe685b415

Tx prefix hash: 2b59bbcbd3d063a010e23dae0fcf765517b94d963e0942ddf3b5b5a46611aae8
Tx public key: f957337e5549e3d87486346f7ef33cbb1cd947520db416539ad2d9a827a8bbd6
Timestamp: 1738701018 Timestamp [UCT]: 2025-02-04 20:30:18 Age [y:d:h:m:s]: 00:289:18:34:25
Block: 1212159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204861 RingCT/type: yes/0
Extra: 01f957337e5549e3d87486346f7ef33cbb1cd947520db416539ad2d9a827a8bbd60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c51b1f4adc7fff341d469db6faf127c054ab4c8832bb96de051e077935874932 0.600000000000 1698930 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": 1212169, "vin": [ { "gen": { "height": 1212159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c51b1f4adc7fff341d469db6faf127c054ab4c8832bb96de051e077935874932" } } ], "extra": [ 1, 249, 87, 51, 126, 85, 73, 227, 216, 116, 134, 52, 111, 126, 243, 60, 187, 28, 217, 71, 82, 13, 180, 22, 83, 154, 210, 217, 168, 39, 168, 187, 214, 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