Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57287f7b2c2ab090a72a58ea0c78d7f550dbfeac62c28d451cb3e935803b090b

Tx prefix hash: f0b695c089d422fe6c25dd8bfb058a35157d9fe1dc3a429257f2051c7305d67c
Tx public key: 4b687a8c1cf790c30baa69deadbebd5c70434768364ebda03f404c924ed9dbef
Timestamp: 1760244083 Timestamp [UCT]: 2025-10-12 04:41:23 Age [y:d:h:m:s]: 00:109:23:40:00
Block: 1388082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78570 RingCT/type: yes/0
Extra: 014b687a8c1cf790c30baa69deadbebd5c70434768364ebda03f404c924ed9dbef021100000005163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74c253666cbc2a6e98e013952633d0fddd2f4d24f715ce327c5af30cd2b5068f 0.600000000000 1876277 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": 1388092, "vin": [ { "gen": { "height": 1388082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74c253666cbc2a6e98e013952633d0fddd2f4d24f715ce327c5af30cd2b5068f" } } ], "extra": [ 1, 75, 104, 122, 140, 28, 247, 144, 195, 11, 170, 105, 222, 173, 190, 189, 92, 112, 67, 71, 104, 54, 78, 189, 160, 63, 64, 76, 146, 78, 217, 219, 239, 2, 17, 0, 0, 0, 5, 22, 49, 145, 238, 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