Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ff9e2d0b4aa469acb93d12c1ce9ab70ea77fedd9fee5f93c3d0fd71dbb8ed31

Tx prefix hash: 3411fd4ffd36e5afec6ba0f608d3636e88fa2bc265fcaeb4cf43084194345b79
Tx public key: 426f7b17544fb2a959e7e6fd0ccca6ea01a13b5f789325246fe243649ce398b3
Timestamp: 1756077077 Timestamp [UCT]: 2025-08-24 23:11:17 Age [y:d:h:m:s]: 00:093:15:21:25
Block: 1353731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66862 RingCT/type: yes/0
Extra: 01426f7b17544fb2a959e7e6fd0ccca6ea01a13b5f789325246fe243649ce398b3021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 370089e3fbb1f87619ba573f4904dbc44bbb233ac4bd096680b2006805c2b5a4 0.600000000000 1841708 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": 1353741, "vin": [ { "gen": { "height": 1353731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "370089e3fbb1f87619ba573f4904dbc44bbb233ac4bd096680b2006805c2b5a4" } } ], "extra": [ 1, 66, 111, 123, 23, 84, 79, 178, 169, 89, 231, 230, 253, 12, 204, 166, 234, 1, 161, 59, 95, 120, 147, 37, 36, 111, 226, 67, 100, 156, 227, 152, 179, 2, 17, 0, 0, 0, 1, 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