Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a204b1944c12d5177b26b3cf8fc2695dcc8241abaa31a8dd071a1a29437f934d

Tx prefix hash: 6d5b9fafc87f21642e1e8bb720823b418beefd2a47abda61956b0f6157c969fe
Tx public key: 52f098c00084ebe8be607031c0b163de236be5db83e1c4bcfeba6357745c3c7b
Timestamp: 1698371825 Timestamp [UCT]: 2023-10-27 01:57:05 Age [y:d:h:m:s]: 01:160:05:08:03
Block: 878462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375503 RingCT/type: yes/0
Extra: 0152f098c00084ebe8be607031c0b163de236be5db83e1c4bcfeba6357745c3c7b0211000000084b8f5122000000000000000000

1 output(s) for total of 0.753890073000 dcy

stealth address amount amount idx
00: 7a3c11fd6c9f0707fcaddbceea1b406174293f0f498051c049cd546aee8aafe9 0.753890073000 1333908 of 0

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": 878472, "vin": [ { "gen": { "height": 878462 } } ], "vout": [ { "amount": 753890073, "target": { "key": "7a3c11fd6c9f0707fcaddbceea1b406174293f0f498051c049cd546aee8aafe9" } } ], "extra": [ 1, 82, 240, 152, 192, 0, 132, 235, 232, 190, 96, 112, 49, 192, 177, 99, 222, 35, 107, 229, 219, 131, 225, 196, 188, 254, 186, 99, 87, 116, 92, 60, 123, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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