Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d95f206828c8c22f1d28d23cb4661dcd2be7c3495cee3d57da29f79e6ac8f0

Tx prefix hash: b512a92687ca325747057b0d24768f18dc8513cd452caa5935f676a1bd40b434
Tx public key: 4b7ee829a1575b10f34dc21f70c2d394680284de120c4467de85f4e85aa61f4c
Timestamp: 1763521503 Timestamp [UCT]: 2025-11-19 03:05:03 Age [y:d:h:m:s]: 00:044:23:03:33
Block: 1415242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32205 RingCT/type: yes/0
Extra: 014b7ee829a1575b10f34dc21f70c2d394680284de120c4467de85f4e85aa61f4c021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8aeb7b076106e5d2955496a1e66ee067361d2237b58e439d4519a3b28ec5819 0.600000000000 1903739 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": 1415252, "vin": [ { "gen": { "height": 1415242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8aeb7b076106e5d2955496a1e66ee067361d2237b58e439d4519a3b28ec5819" } } ], "extra": [ 1, 75, 126, 232, 41, 161, 87, 91, 16, 243, 77, 194, 31, 112, 194, 211, 148, 104, 2, 132, 222, 18, 12, 68, 103, 222, 133, 244, 232, 90, 166, 31, 76, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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