Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a6c6962c66e621443a723aad672419575e71e6370246eca7ecd0ffd04e825c

Tx prefix hash: d73267980675ee7f6383d9c6090145283d99e22ff08252daae69ec0f2da43ce8
Tx public key: 1f7836b22971f00f752888aecf756efcbfa7b278a01d85f9d0ef0e67f224d9e5
Timestamp: 1718303400 Timestamp [UCT]: 2024-06-13 18:30:00 Age [y:d:h:m:s]: 00:275:04:48:20
Block: 1043494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196679 RingCT/type: yes/0
Extra: 011f7836b22971f00f752888aecf756efcbfa7b278a01d85f9d0ef0e67f224d9e50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aae5a6a0de57754c9bf7be6e5cb0592add82c55b71f0ffb95e7cfc0ccdc5964 0.600000000000 1512647 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": 1043504, "vin": [ { "gen": { "height": 1043494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aae5a6a0de57754c9bf7be6e5cb0592add82c55b71f0ffb95e7cfc0ccdc5964" } } ], "extra": [ 1, 31, 120, 54, 178, 41, 113, 240, 15, 117, 40, 136, 174, 207, 117, 110, 252, 191, 167, 178, 120, 160, 29, 133, 249, 208, 239, 14, 103, 242, 36, 217, 229, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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