Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 876e8a1311a614a802d182c2557a53f99957f6c29efdaf8170eebd4378a7c976

Tx prefix hash: 1bbdf805ddede9601ccb35eb530bdbc9ad0c92fad033b1bbf5b7a4fa7e0ddd8a
Tx public key: 04e2b0bec9dee555d90ae28d5cdf122aa3717d5cc7c847db305e894170c50e15
Timestamp: 1763169912 Timestamp [UCT]: 2025-11-15 01:25:12 Age [y:d:h:m:s]: 00:012:19:31:48
Block: 1412333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9175 RingCT/type: yes/0
Extra: 0104e2b0bec9dee555d90ae28d5cdf122aa3717d5cc7c847db305e894170c50e15021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83d88318f41a8d187587da68a5d65d470be8ba4166fba608742f9ba1515967d1 0.600000000000 1900800 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": 1412343, "vin": [ { "gen": { "height": 1412333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83d88318f41a8d187587da68a5d65d470be8ba4166fba608742f9ba1515967d1" } } ], "extra": [ 1, 4, 226, 176, 190, 201, 222, 229, 85, 217, 10, 226, 141, 92, 223, 18, 42, 163, 113, 125, 92, 199, 200, 71, 219, 48, 94, 137, 65, 112, 197, 14, 21, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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