Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a33693c53415e2a4e59ec9597d4e1c21a759a8c4fd6972902bb12c546287d079

Tx prefix hash: 8ef96b4fa3cc435549f179e8b35371acbbe93c49c7c2d1d4a223aaf156003bc3
Tx public key: 24bd78672428181a73e5157ca095b2bab37a8a2ce84aa2e9db61cfb838dc2b12
Timestamp: 1757576169 Timestamp [UCT]: 2025-09-11 07:36:09 Age [y:d:h:m:s]: 00:112:14:09:06
Block: 1365984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80605 RingCT/type: yes/0
Extra: 0124bd78672428181a73e5157ca095b2bab37a8a2ce84aa2e9db61cfb838dc2b12021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6efa8652a0ab433f712e1c1199a0ca0f62d6c1bff7e6ceaa5622d9454e4699 0.600000000000 1854023 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": 1365994, "vin": [ { "gen": { "height": 1365984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6efa8652a0ab433f712e1c1199a0ca0f62d6c1bff7e6ceaa5622d9454e4699" } } ], "extra": [ 1, 36, 189, 120, 103, 36, 40, 24, 26, 115, 229, 21, 124, 160, 149, 178, 186, 179, 122, 138, 44, 232, 74, 162, 233, 219, 97, 207, 184, 56, 220, 43, 18, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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