Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68a193208fc3c50dc7217217659c8347787bc78990b62a9eabe2ea8e1aec665a

Tx prefix hash: 0f4fb8280e9d05b1b53987402b4742bbc7c1b8f22848b474ac4f4aea94193e21
Tx public key: b5a2fd87cbf065d0d8e5c54063b711a5ed13c8370803375e3239221ab20c9150
Timestamp: 1724874189 Timestamp [UCT]: 2024-08-28 19:43:09 Age [y:d:h:m:s]: 00:291:10:14:05
Block: 1097961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208090 RingCT/type: yes/0
Extra: 01b5a2fd87cbf065d0d8e5c54063b711a5ed13c8370803375e3239221ab20c915002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc0e9a73998d815fa9887a6bee6c181ab17557a78117d77a20b01e75f194991 0.600000000000 1573510 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": 1097971, "vin": [ { "gen": { "height": 1097961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc0e9a73998d815fa9887a6bee6c181ab17557a78117d77a20b01e75f194991" } } ], "extra": [ 1, 181, 162, 253, 135, 203, 240, 101, 208, 216, 229, 197, 64, 99, 183, 17, 165, 237, 19, 200, 55, 8, 3, 55, 94, 50, 57, 34, 26, 178, 12, 145, 80, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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