Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e8063a9ba7426f9356f229cf40a47b4d0b8830f69d24aeb174e6b49c3044d74

Tx prefix hash: 30a3be1ad0f776b71d14529e85aaaf548b914bbab3c5b0085f7117e59b9a1b79
Tx public key: d0aada16dbd10c21d39cab2d05385824bb7d3a7b7dacde06bfd807d21ce79860
Timestamp: 1694912145 Timestamp [UCT]: 2023-09-17 00:55:45 Age [y:d:h:m:s]: 01:116:04:17:38
Block: 849754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344341 RingCT/type: yes/0
Extra: 01d0aada16dbd10c21d39cab2d05385824bb7d3a7b7dacde06bfd807d21ce79860021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.938452521000 dcy

stealth address amount amount idx
00: 4e43f5514e7e6bfd0b4c0e814c7b31e8dd9f749dbd2a17b91d550d953145bbbb 0.938452521000 1303432 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": 849764, "vin": [ { "gen": { "height": 849754 } } ], "vout": [ { "amount": 938452521, "target": { "key": "4e43f5514e7e6bfd0b4c0e814c7b31e8dd9f749dbd2a17b91d550d953145bbbb" } } ], "extra": [ 1, 208, 170, 218, 22, 219, 209, 12, 33, 211, 156, 171, 45, 5, 56, 88, 36, 187, 125, 58, 123, 125, 172, 222, 6, 191, 216, 7, 210, 28, 231, 152, 96, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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