Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 257cdcd608f285ea09ad387e0f97c709eaf4e84421cef2c5d0491934aa1a0c9a

Tx prefix hash: 5aabd4053a2b2979680747e353edca0152f7dfcd5df14d11623b819c8fee84e7
Tx public key: 60ad95c234a69fcc197df417a098e5002d5c2485ec59a2cfa3f5b85f9263f4b2
Timestamp: 1753880298 Timestamp [UCT]: 2025-07-30 12:58:18 Age [y:d:h:m:s]: 00:119:03:19:03
Block: 1336650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84005 RingCT/type: yes/0
Extra: 0160ad95c234a69fcc197df417a098e5002d5c2485ec59a2cfa3f5b85f9263f4b2021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770e45b542110393714ff7057713b0d739b510cf00fefed430160264083b23a9 0.600000000000 1824451 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": 1336660, "vin": [ { "gen": { "height": 1336650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770e45b542110393714ff7057713b0d739b510cf00fefed430160264083b23a9" } } ], "extra": [ 1, 96, 173, 149, 194, 52, 166, 159, 204, 25, 125, 244, 23, 160, 152, 229, 0, 45, 92, 36, 133, 236, 89, 162, 207, 163, 245, 184, 95, 146, 99, 244, 178, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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