Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a3866506e0833915df3b47b8fb98c4711f78130b1165a3a3fc51aa5794a44ce

Tx prefix hash: 4faf3373a27d0134e251d9070557f52fcb90eab984131b3d2244f305ecd964a7
Tx public key: 72c3931ec56a16aff520a2972885940d3e0f1583270f3e421b9650b470037b68
Timestamp: 1705258538 Timestamp [UCT]: 2024-01-14 18:55:38 Age [y:d:h:m:s]: 01:103:18:03:45
Block: 935327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335273 RingCT/type: yes/0
Extra: 0172c3931ec56a16aff520a2972885940d3e0f1583270f3e421b9650b470037b680211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe599d0f7b21c2e6b4e6f85b7af80f3d2afbdf45653d39d20e3b01b2d0082fd2 0.600000000000 1393343 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": 935337, "vin": [ { "gen": { "height": 935327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe599d0f7b21c2e6b4e6f85b7af80f3d2afbdf45653d39d20e3b01b2d0082fd2" } } ], "extra": [ 1, 114, 195, 147, 30, 197, 106, 22, 175, 245, 32, 162, 151, 40, 133, 148, 13, 62, 15, 21, 131, 39, 15, 62, 66, 27, 150, 80, 180, 112, 3, 123, 104, 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