Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c0d19e24cf99fc5d48da8f4adb47b84ba4b89742c3b19cafba2211cdba683e4

Tx prefix hash: 2fe0e8733b43c9ac03c9f975e31a31649ee6a87bfdbe1c1e9ed2c19c24cbe5f2
Tx public key: db8bfa27393fac97beff6bc49c6b6a2e56092910a9053bf3a26cb7950115bcd4
Timestamp: 1725395791 Timestamp [UCT]: 2024-09-03 20:36:31 Age [y:d:h:m:s]: 00:211:04:15:17
Block: 1102294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150757 RingCT/type: yes/0
Extra: 01db8bfa27393fac97beff6bc49c6b6a2e56092910a9053bf3a26cb7950115bcd4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd31030e94f7fba2cc0091dc549f6fe9de3b9274ab631f605501be7fa542e272 0.600000000000 1578673 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": 1102304, "vin": [ { "gen": { "height": 1102294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd31030e94f7fba2cc0091dc549f6fe9de3b9274ab631f605501be7fa542e272" } } ], "extra": [ 1, 219, 139, 250, 39, 57, 63, 172, 151, 190, 255, 107, 196, 156, 107, 106, 46, 86, 9, 41, 16, 169, 5, 59, 243, 162, 108, 183, 149, 1, 21, 188, 212, 2, 17, 0, 0, 0, 5, 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