Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2db3593241010a4bef032b6be8789b47f51640b2cc4b5c76017cabef84067cf

Tx prefix hash: dbb66b640be298f2a346524d831114590c53d317d905f46993f1a784c0a08d5b
Tx public key: 74fd4c61f857f97666031fbb7532f407f9193b8d3c6baab99f78844f3fd8f376
Timestamp: 1755328554 Timestamp [UCT]: 2025-08-16 07:15:54 Age [y:d:h:m:s]: 00:096:00:45:35
Block: 1347694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68413 RingCT/type: yes/0
Extra: 0174fd4c61f857f97666031fbb7532f407f9193b8d3c6baab99f78844f3fd8f3760211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65ee5771c7df90957c985abea2ffb380fe6b2eb7150f7ee91fa208eeef800b22 0.600000000000 1835615 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": 1347704, "vin": [ { "gen": { "height": 1347694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65ee5771c7df90957c985abea2ffb380fe6b2eb7150f7ee91fa208eeef800b22" } } ], "extra": [ 1, 116, 253, 76, 97, 248, 87, 249, 118, 102, 3, 31, 187, 117, 50, 244, 7, 249, 25, 59, 141, 60, 107, 170, 185, 159, 120, 132, 79, 63, 216, 243, 118, 2, 17, 0, 0, 0, 2, 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