Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c67d3660c697ea5a54ef0a0170364ba1f5609ffa01964a9450fcf9cfe5cf63

Tx prefix hash: eb868ab2685387408b33a4586cef8e44f6ed46f46cda3779ea18544af5462a66
Tx public key: 548358d7ed2619d0cf3bf48bd820859ea2d46e95ad3d68d617f2de76a796c1e9
Timestamp: 1764772934 Timestamp [UCT]: 2025-12-03 14:42:14 Age [y:d:h:m:s]: 00:058:13:22:46
Block: 1425633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41726 RingCT/type: yes/0
Extra: 01548358d7ed2619d0cf3bf48bd820859ea2d46e95ad3d68d617f2de76a796c1e9021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3b1caa3864bc42f0c856ee70828599b8939cb8eb0fcae2fa00a3acc7b6dd5f 0.600000000000 1914298 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": 1425643, "vin": [ { "gen": { "height": 1425633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3b1caa3864bc42f0c856ee70828599b8939cb8eb0fcae2fa00a3acc7b6dd5f" } } ], "extra": [ 1, 84, 131, 88, 215, 237, 38, 25, 208, 207, 59, 244, 139, 216, 32, 133, 158, 162, 212, 110, 149, 173, 61, 104, 214, 23, 242, 222, 118, 167, 150, 193, 233, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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