Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad9ce46be9a81b3ddc4f9eb4b03d73d30727b49262bf8c53c3039a08074b94e3

Tx prefix hash: 524433253017865d3919617f158a7df636a968a0e00e0547dd227014aae88df9
Tx public key: 96d6d0821dfafcbecec57b879e26e0e0548a2ec142c09f41c536fde46d50fee4
Timestamp: 1764347318 Timestamp [UCT]: 2025-11-28 16:28:38 Age [y:d:h:m:s]: 00:065:12:16:26
Block: 1422095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46714 RingCT/type: yes/0
Extra: 0196d6d0821dfafcbecec57b879e26e0e0548a2ec142c09f41c536fde46d50fee402110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5427e46f40ca4e8df32d69c609c2e9210f611ce17f4e46ab3d343f3aa4d3f0 0.600000000000 1910660 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": 1422105, "vin": [ { "gen": { "height": 1422095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5427e46f40ca4e8df32d69c609c2e9210f611ce17f4e46ab3d343f3aa4d3f0" } } ], "extra": [ 1, 150, 214, 208, 130, 29, 250, 252, 190, 206, 197, 123, 135, 158, 38, 224, 224, 84, 138, 46, 193, 66, 192, 159, 65, 197, 54, 253, 228, 109, 80, 254, 228, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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