Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2b6f170e77ed8c9ed96f87ae9a57cb3b4bd77ea83166ba775649e45e2577cb

Tx prefix hash: 5eb0535a9b6dd617789b6c5adbe04f3f197daf0c17dd096dcad9d574deeb55de
Tx public key: ab64c54e9dd18a24d940a590d48b635a0401a3008f3524e2d8710922d046071a
Timestamp: 1751588906 Timestamp [UCT]: 2025-07-04 00:28:26 Age [y:d:h:m:s]: 00:140:23:59:41
Block: 1318266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99041 RingCT/type: yes/0
Extra: 01ab64c54e9dd18a24d940a590d48b635a0401a3008f3524e2d8710922d046071a021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d4de620121aa62dcce32da24e90770ecd5188aea1ce9c87f3c769866b5e1030 0.600000000000 1805943 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": 1318276, "vin": [ { "gen": { "height": 1318266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d4de620121aa62dcce32da24e90770ecd5188aea1ce9c87f3c769866b5e1030" } } ], "extra": [ 1, 171, 100, 197, 78, 157, 209, 138, 36, 217, 64, 165, 144, 212, 139, 99, 90, 4, 1, 163, 0, 143, 53, 36, 226, 216, 113, 9, 34, 208, 70, 7, 26, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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