Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f769a5234d03ef8b7c93d1ebec4046b65d681f136f0df652a2db952be18c3949

Tx prefix hash: fb20aa74589e73a5aede6665a9718ef52751d57258f57f5e32cff7fb363ae67c
Tx public key: bc5d7dc51ad891c0820c1d7dc42714ab1493443d265e17cf440c23d7d949b1ba
Timestamp: 1732953720 Timestamp [UCT]: 2024-11-30 08:02:00 Age [y:d:h:m:s]: 00:114:16:06:14
Block: 1164848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81748 RingCT/type: yes/0
Extra: 01bc5d7dc51ad891c0820c1d7dc42714ab1493443d265e17cf440c23d7d949b1ba021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 412be36cf4b63089cc5c32a204ac28c6cfe9cc2021731db8ec934e519769f290 0.600000000000 1650523 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": 1164858, "vin": [ { "gen": { "height": 1164848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "412be36cf4b63089cc5c32a204ac28c6cfe9cc2021731db8ec934e519769f290" } } ], "extra": [ 1, 188, 93, 125, 197, 26, 216, 145, 192, 130, 12, 29, 125, 196, 39, 20, 171, 20, 147, 68, 61, 38, 94, 23, 207, 68, 12, 35, 215, 217, 73, 177, 186, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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