Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc09801ee349f40bc59bff9053005267446f1186759f4b9cf335ad09fb3a79cc

Tx prefix hash: 316a14b63f0f7591449721f98ff2e5f3bb95ded28c9e99f521b559503b88162d
Tx public key: b021b5526687b71bc4b8c105cd706986839562854d146f6cb4a1c0d06b337089
Timestamp: 1726898935 Timestamp [UCT]: 2024-09-21 06:08:55 Age [y:d:h:m:s]: 01:050:00:56:06
Block: 1114749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294169 RingCT/type: yes/0
Extra: 01b021b5526687b71bc4b8c105cd706986839562854d146f6cb4a1c0d06b337089021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbd8274a1f26f2512ec713b4c8b831e899c1b7201a711c2b04da36fd3d1cb3db 0.600000000000 1594638 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": 1114759, "vin": [ { "gen": { "height": 1114749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbd8274a1f26f2512ec713b4c8b831e899c1b7201a711c2b04da36fd3d1cb3db" } } ], "extra": [ 1, 176, 33, 181, 82, 102, 135, 183, 27, 196, 184, 193, 5, 205, 112, 105, 134, 131, 149, 98, 133, 77, 20, 111, 108, 180, 161, 192, 208, 107, 51, 112, 137, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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