Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afbd21e37c02c07df1a03c1065d3a95a0aae75a3b1e2425d85e9ee6f395383d6

Tx prefix hash: 269c2f5e17143defc4e14154bc7e3a191d840fce6aa80de8d4d48fa4499b05e0
Tx public key: 62036fd3e8c1e773c0602865a6e6f700afce24cc4cd3907c4589dcb7a963e989
Timestamp: 1763366258 Timestamp [UCT]: 2025-11-17 07:57:38 Age [y:d:h:m:s]: 00:010:23:25:36
Block: 1413953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7861 RingCT/type: yes/0
Extra: 0162036fd3e8c1e773c0602865a6e6f700afce24cc4cd3907c4589dcb7a963e989021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc30c26bcbf2614d007fefd21c025de22098f5c0bdba8fb5a0e7c2cfd914955 0.600000000000 1902436 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": 1413963, "vin": [ { "gen": { "height": 1413953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc30c26bcbf2614d007fefd21c025de22098f5c0bdba8fb5a0e7c2cfd914955" } } ], "extra": [ 1, 98, 3, 111, 211, 232, 193, 231, 115, 192, 96, 40, 101, 166, 230, 247, 0, 175, 206, 36, 204, 76, 211, 144, 124, 69, 137, 220, 183, 169, 99, 233, 137, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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