Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da20f86b84d6bccaa8c549884d28e7f3337e64d641205c47fda06c3ccc5adb72

Tx prefix hash: dd01df12e017e8b706bec04b32b742f89de2a88c7ac719a8adfbeb5ee8df012d
Tx public key: 634cb5ad125b17812a2075f67f5fcd783878ae76b161766f1cb3dda9b3d293c9
Timestamp: 1766260706 Timestamp [UCT]: 2025-12-20 19:58:26 Age [y:d:h:m:s]: 00:001:04:18:40
Block: 1437944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846 RingCT/type: yes/0
Extra: 01634cb5ad125b17812a2075f67f5fcd783878ae76b161766f1cb3dda9b3d293c90211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b21072c5572dfb9f9f89ec0e5da216239bb15ca6db43f71cfa56e80aa185a2d 0.600000000000 1926757 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": 1437954, "vin": [ { "gen": { "height": 1437944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b21072c5572dfb9f9f89ec0e5da216239bb15ca6db43f71cfa56e80aa185a2d" } } ], "extra": [ 1, 99, 76, 181, 173, 18, 91, 23, 129, 42, 32, 117, 246, 127, 95, 205, 120, 56, 120, 174, 118, 177, 97, 118, 111, 28, 179, 221, 169, 179, 210, 147, 201, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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