Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab40c2404a4fbbd7e67a8f4b1589c9e1a35f9abf1c195a2e6f9f6f560d289c35

Tx prefix hash: 6f27c3a99a41c4464d32182ae83783792103e93693f9dbb888d4f977efd6c103
Tx public key: 4571d8d8a73dc1e71b4a72ba16e71ae6e94b910f173237f3a757022f23bf64fa
Timestamp: 1704038890 Timestamp [UCT]: 2023-12-31 16:08:10 Age [y:d:h:m:s]: 02:032:21:52:07
Block: 925220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543152 RingCT/type: yes/0
Extra: 014571d8d8a73dc1e71b4a72ba16e71ae6e94b910f173237f3a757022f23bf64fa0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f52ae7f94727486dab617b1892929498081ac2df7a95cc34a1d67f54b964c4e 0.600000000000 1382980 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": 925230, "vin": [ { "gen": { "height": 925220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f52ae7f94727486dab617b1892929498081ac2df7a95cc34a1d67f54b964c4e" } } ], "extra": [ 1, 69, 113, 216, 216, 167, 61, 193, 231, 27, 74, 114, 186, 22, 231, 26, 230, 233, 75, 145, 15, 23, 50, 55, 243, 167, 87, 2, 47, 35, 191, 100, 250, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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