Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51638f3e731f7ed013946a2ca0c1c171266c5faf5c373ce85620e665105f7b61

Tx prefix hash: 2cc171ebcabacb849d27b676378a46de08bd35a73f6558595b3f614b6a112329
Tx public key: f58dbcbbc3c0b478b5b3e59dfcf3c7ecd1bcd81f816c344b8ebe74c9ed565951
Timestamp: 1709168483 Timestamp [UCT]: 2024-02-29 01:01:23 Age [y:d:h:m:s]: 01:078:01:59:33
Block: 967763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316841 RingCT/type: yes/0
Extra: 01f58dbcbbc3c0b478b5b3e59dfcf3c7ecd1bcd81f816c344b8ebe74c9ed5659510211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe894635fb326f44080a3b9e69bc25f594800b9fa7a93bf6272628eb481beab 0.600000000000 1427548 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": 967773, "vin": [ { "gen": { "height": 967763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe894635fb326f44080a3b9e69bc25f594800b9fa7a93bf6272628eb481beab" } } ], "extra": [ 1, 245, 141, 188, 187, 195, 192, 180, 120, 181, 179, 229, 157, 252, 243, 199, 236, 209, 188, 216, 31, 129, 108, 52, 75, 142, 190, 116, 201, 237, 86, 89, 81, 2, 17, 0, 0, 0, 4, 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