Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d127ad9833bd6475f6a29df093f13a9421c693a2803a8baf05ffd9a4f278c4bd

Tx prefix hash: d58826b44085479811e3aff5dae7be0955f5c8527779af0a49c570e2503aa0c7
Tx public key: 1b22a7768fb725dc99b5abec958432f75ee18df41c6d27b9b932817260de45c8
Timestamp: 1725828761 Timestamp [UCT]: 2024-09-08 20:52:41 Age [y:d:h:m:s]: 00:120:14:23:12
Block: 1105882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86242 RingCT/type: yes/0
Extra: 011b22a7768fb725dc99b5abec958432f75ee18df41c6d27b9b932817260de45c8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56692edb21d9c4ed03d3818dc1018d16ebdc4974d0d779e274a56e9955130979 0.600000000000 1583375 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": 1105892, "vin": [ { "gen": { "height": 1105882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56692edb21d9c4ed03d3818dc1018d16ebdc4974d0d779e274a56e9955130979" } } ], "extra": [ 1, 27, 34, 167, 118, 143, 183, 37, 220, 153, 181, 171, 236, 149, 132, 50, 247, 94, 225, 141, 244, 28, 109, 39, 185, 185, 50, 129, 114, 96, 222, 69, 200, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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