Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901c4884a036236c14c2798fb14322d889452ea232e6829594f469cbc3d0f058

Tx prefix hash: f9cc0332268e37d648ddac40f55f18dc80f7fe0c986995e4a70d3a924ff43002
Tx public key: b0dd8048f0ac1b95c19a63ab4dea63187631b46158e7e4cb65591f877f6c9cfb
Timestamp: 1703703104 Timestamp [UCT]: 2023-12-27 18:51:44 Age [y:d:h:m:s]: 01:111:17:18:37
Block: 922446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340965 RingCT/type: yes/0
Extra: 01b0dd8048f0ac1b95c19a63ab4dea63187631b46158e7e4cb65591f877f6c9cfb021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2e14dae9e8549e14cf15fd9a1452a8af5e0d401ad3d9740df7becd2f28ee9bf 0.600000000000 1380142 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": 922456, "vin": [ { "gen": { "height": 922446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2e14dae9e8549e14cf15fd9a1452a8af5e0d401ad3d9740df7becd2f28ee9bf" } } ], "extra": [ 1, 176, 221, 128, 72, 240, 172, 27, 149, 193, 154, 99, 171, 77, 234, 99, 24, 118, 49, 180, 97, 88, 231, 228, 203, 101, 89, 31, 135, 127, 108, 156, 251, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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