Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9645129e18d6c00b270a71821992b505f665d621b9c788053404cb49319a2526

Tx prefix hash: 7dea714da3316c04cd850d1563d12521ca6d3916db3e178f5bb582875c65a9f0
Tx public key: 9b83825f768e7cab67d5b2f84da500e71b9b6937e9a73819b20a234b71049ced
Timestamp: 1735056128 Timestamp [UCT]: 2024-12-24 16:02:08 Age [y:d:h:m:s]: 00:099:17:00:27
Block: 1182269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71029 RingCT/type: yes/0
Extra: 019b83825f768e7cab67d5b2f84da500e71b9b6937e9a73819b20a234b71049ced0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f38dcbbba8066f89a12da06d4935a6b364b0b61379b5d657087cfd6d5a26e36 0.600000000000 1668702 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": 1182279, "vin": [ { "gen": { "height": 1182269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f38dcbbba8066f89a12da06d4935a6b364b0b61379b5d657087cfd6d5a26e36" } } ], "extra": [ 1, 155, 131, 130, 95, 118, 142, 124, 171, 103, 213, 178, 248, 77, 165, 0, 231, 27, 155, 105, 55, 233, 167, 56, 25, 178, 10, 35, 75, 113, 4, 156, 237, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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