Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e8f3be1d6b84cb4b262021d079c782da1d60d66119c82d156395516ca86951c

Tx prefix hash: f4dd1a6ac746153aaded8a1513937cc6b9ecd3080f7cd8b414bc1101e8befed0
Tx public key: 707a26d7e41ff449e654106f36fdf24b433c1a67651b19f4a5f4796b8df0cd98
Timestamp: 1734532453 Timestamp [UCT]: 2024-12-18 14:34:13 Age [y:d:h:m:s]: 00:109:15:08:33
Block: 1177950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78101 RingCT/type: yes/0
Extra: 01707a26d7e41ff449e654106f36fdf24b433c1a67651b19f4a5f4796b8df0cd980211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19326e352a507a166c0e6189dc3364c0f371df6f2c9ffe5591efd05f31134e64 0.600000000000 1664331 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": 1177960, "vin": [ { "gen": { "height": 1177950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19326e352a507a166c0e6189dc3364c0f371df6f2c9ffe5591efd05f31134e64" } } ], "extra": [ 1, 112, 122, 38, 215, 228, 31, 244, 73, 230, 84, 16, 111, 54, 253, 242, 75, 67, 60, 26, 103, 101, 27, 25, 244, 165, 244, 121, 107, 141, 240, 205, 152, 2, 17, 0, 0, 0, 2, 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