Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f0a8b2ccd45dfe26eb312170a96ae4c2cbd977f85b5e5cf034c7b30b881c1fb

Tx prefix hash: 1638c8d2b00bcb7976dd081446b566335f01f17d4afe4034768d58576fbbab6f
Tx public key: 999764cc9964bc0d0dbc35d6c204fda1d2b2163741215bb2be53b48d64211c7b
Timestamp: 1703097506 Timestamp [UCT]: 2023-12-20 18:38:26 Age [y:d:h:m:s]: 01:145:07:05:25
Block: 917445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364980 RingCT/type: yes/0
Extra: 01999764cc9964bc0d0dbc35d6c204fda1d2b2163741215bb2be53b48d64211c7b021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06653031781ab5969c2274368ea9c0e1c33a626049fa79dfa77ead6c2c04fab9 0.600000000000 1375027 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": 917455, "vin": [ { "gen": { "height": 917445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06653031781ab5969c2274368ea9c0e1c33a626049fa79dfa77ead6c2c04fab9" } } ], "extra": [ 1, 153, 151, 100, 204, 153, 100, 188, 13, 13, 188, 53, 214, 194, 4, 253, 161, 210, 178, 22, 55, 65, 33, 91, 178, 190, 83, 180, 141, 100, 33, 28, 123, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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