Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7086a637e5e7795083e107dcc7376c0ebff6ef6731e306e605ad7705543f4a4d

Tx prefix hash: 503fda12464ee60ba84d994dc33d191a7c20be6982f7154802a83c1a9185dc88
Tx public key: f98b267fde4cf6cee32a6b01a05dfad4fbf01434fa3b5ce9fad969fae70639cf
Timestamp: 1754102358 Timestamp [UCT]: 2025-08-02 02:39:18 Age [y:d:h:m:s]: 00:110:05:43:45
Block: 1338435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77679 RingCT/type: yes/0
Extra: 01f98b267fde4cf6cee32a6b01a05dfad4fbf01434fa3b5ce9fad969fae70639cf0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e7e733c8f74b29d373bde4ad476833b0fff87405a5afdf29a071f7747e27ef 0.600000000000 1826244 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": 1338445, "vin": [ { "gen": { "height": 1338435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e7e733c8f74b29d373bde4ad476833b0fff87405a5afdf29a071f7747e27ef" } } ], "extra": [ 1, 249, 139, 38, 127, 222, 76, 246, 206, 227, 42, 107, 1, 160, 93, 250, 212, 251, 240, 20, 52, 250, 59, 92, 233, 250, 217, 105, 250, 231, 6, 57, 207, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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