Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ffb0d02a70c45f351cff1a5320d33631d19173a9656d0e63781e216dbf67c63

Tx prefix hash: c70660c8ed80f2fd497d8cd7b45d9c79fa995852c868c9def65442e076870e39
Tx public key: 8b0e5f3a98f9bc5a834a7964a768a8040bbc31b17f4e79ee9da656ae900c18df
Timestamp: 1754604158 Timestamp [UCT]: 2025-08-07 22:02:38 Age [y:d:h:m:s]: 00:104:06:57:51
Block: 1342402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73618 RingCT/type: yes/0
Extra: 018b0e5f3a98f9bc5a834a7964a768a8040bbc31b17f4e79ee9da656ae900c18df0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db84fa6b737b504e94e76bea59d60fca79d046e90a354ba78ef04b630c35cab0 0.600000000000 1830233 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": 1342412, "vin": [ { "gen": { "height": 1342402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db84fa6b737b504e94e76bea59d60fca79d046e90a354ba78ef04b630c35cab0" } } ], "extra": [ 1, 139, 14, 95, 58, 152, 249, 188, 90, 131, 74, 121, 100, 167, 104, 168, 4, 11, 188, 49, 177, 127, 78, 121, 238, 157, 166, 86, 174, 144, 12, 24, 223, 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