Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb526456ff94a7ad6b33b26c4dce32058ff08a62db70911c68b0a8e1b8629b0b

Tx prefix hash: 200f637a2d2c49e333299c8b45cd0471f8bec131a70a3c86b4f684a5df3dbbc6
Tx public key: b7b259a2e80901b2f4ff470ac944be6d1892306f069cec1d8514e6e486ede626
Timestamp: 1765516433 Timestamp [UCT]: 2025-12-12 05:13:53 Age [y:d:h:m:s]: 00:010:21:20:36
Block: 1431772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7805 RingCT/type: yes/0
Extra: 01b7b259a2e80901b2f4ff470ac944be6d1892306f069cec1d8514e6e486ede62602110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a078b940039152f91ee5fa7f3f399f41c8a5615334d501025ab3531b4ed87f9 0.600000000000 1920545 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": 1431782, "vin": [ { "gen": { "height": 1431772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a078b940039152f91ee5fa7f3f399f41c8a5615334d501025ab3531b4ed87f9" } } ], "extra": [ 1, 183, 178, 89, 162, 232, 9, 1, 178, 244, 255, 71, 10, 201, 68, 190, 109, 24, 146, 48, 111, 6, 156, 236, 29, 133, 20, 230, 228, 134, 237, 230, 38, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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