Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb74f9e77bc3a071b45a382b448c803b3cfbb6498133a43fe441cb26d90f7445

Tx prefix hash: e9aeafd740d56dd2cb8f3b48b2cb3f218d9184b8681aceeba83e6e21b898c316
Tx public key: 197e57c013c149095e3b32aedb1825fabb401f42a174081d0efde7e42b27e613
Timestamp: 1730276322 Timestamp [UCT]: 2024-10-30 08:18:42 Age [y:d:h:m:s]: 00:083:23:26:03
Block: 1142682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60036 RingCT/type: yes/0
Extra: 01197e57c013c149095e3b32aedb1825fabb401f42a174081d0efde7e42b27e6130211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9852b5f9c9841fb92d6e4a7a0a78f7ea1072c1ace8c42cca71dad0edd75c3e1 0.600000000000 1626537 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": 1142692, "vin": [ { "gen": { "height": 1142682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9852b5f9c9841fb92d6e4a7a0a78f7ea1072c1ace8c42cca71dad0edd75c3e1" } } ], "extra": [ 1, 25, 126, 87, 192, 19, 193, 73, 9, 94, 59, 50, 174, 219, 24, 37, 250, 187, 64, 31, 66, 161, 116, 8, 29, 14, 253, 231, 228, 43, 39, 230, 19, 2, 17, 0, 0, 0, 1, 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