Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cabf6aaf6bb19882bbb4e5a691dde45ac4b5f9707cafdd1cbc809360248a94c7

Tx prefix hash: dfabb55cb7beed15848a1e77a6d9064ecf6f1c83a77e66b298bb15d2fbff7a02
Tx public key: cf4ab8e8dfa1ca791654adacefb06b10a58d6c5c1e395273dd083a25b497b051
Timestamp: 1730662142 Timestamp [UCT]: 2024-11-03 19:29:02 Age [y:d:h:m:s]: 00:153:10:37:19
Block: 1145869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109494 RingCT/type: yes/0
Extra: 01cf4ab8e8dfa1ca791654adacefb06b10a58d6c5c1e395273dd083a25b497b0510211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17702a2911551a21ac428286eb8daafb36586e58157dedd318e62a077c70303e 0.600000000000 1630396 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": 1145879, "vin": [ { "gen": { "height": 1145869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17702a2911551a21ac428286eb8daafb36586e58157dedd318e62a077c70303e" } } ], "extra": [ 1, 207, 74, 184, 232, 223, 161, 202, 121, 22, 84, 173, 172, 239, 176, 107, 16, 165, 141, 108, 92, 30, 57, 82, 115, 221, 8, 58, 37, 180, 151, 176, 81, 2, 17, 0, 0, 0, 4, 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