Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0822a52c45e90d4537171d3e9173e4d36ee3025584b09d744b0e9c0b8a1696e1

Tx prefix hash: 7f0f6f469e3febc8b610f7dc1e1bbd1769512cafa8a880604a5ca9e1659d2af8
Tx public key: e6c7997f3695954ab205a6ec69281dd2601887c2b02894038cb4497eb7d2c0d4
Timestamp: 1733500716 Timestamp [UCT]: 2024-12-06 15:58:36 Age [y:d:h:m:s]: 00:111:23:37:18
Block: 1169379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79831 RingCT/type: yes/0
Extra: 01e6c7997f3695954ab205a6ec69281dd2601887c2b02894038cb4497eb7d2c0d40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46059c95b6023197d0ab6adbb48c9983d082ab33ae376d6b673c364640200057 0.600000000000 1655096 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": 1169389, "vin": [ { "gen": { "height": 1169379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46059c95b6023197d0ab6adbb48c9983d082ab33ae376d6b673c364640200057" } } ], "extra": [ 1, 230, 199, 153, 127, 54, 149, 149, 74, 178, 5, 166, 236, 105, 40, 29, 210, 96, 24, 135, 194, 176, 40, 148, 3, 140, 180, 73, 126, 183, 210, 192, 212, 2, 17, 0, 0, 0, 3, 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