Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f43296193fa3a0c25796c5d2d4f193bf5367e896034a85bca1305c172edf07

Tx prefix hash: 836d4a062cfd063a8e458289ec51199e72ab56f2274d7a74405c55a62f176ace
Tx public key: 08f24c7ecb631ee1d341370061e6e6390ce9c5459214b915eab4b712d86a35a9
Timestamp: 1746440543 Timestamp [UCT]: 2025-05-05 10:22:23 Age [y:d:h:m:s]: 00:000:10:21:17
Block: 1276227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314 RingCT/type: yes/0
Extra: 0108f24c7ecb631ee1d341370061e6e6390ce9c5459214b915eab4b712d86a35a90211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f021a46391e42e6a92424d0b8b4a65d55d7d042642d29002a03452c68ec6c3b 0.600000000000 1763552 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": 1276237, "vin": [ { "gen": { "height": 1276227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f021a46391e42e6a92424d0b8b4a65d55d7d042642d29002a03452c68ec6c3b" } } ], "extra": [ 1, 8, 242, 76, 126, 203, 99, 30, 225, 211, 65, 55, 0, 97, 230, 230, 57, 12, 233, 197, 69, 146, 20, 185, 21, 234, 180, 183, 18, 216, 106, 53, 169, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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