Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df63a4781765f917d57a83b23a7696f7c1db14de6e295a03c92f51b5dd14541

Tx prefix hash: 6c4aebf9b543a2d63fbe797e39554a25f2bcd26253b00fd3466e4a3f531a922d
Tx public key: 5c756fe282709ff0f484ac91e00488fd87b1cbe8e65168cdee3b1b9bbabf2d99
Timestamp: 1763789692 Timestamp [UCT]: 2025-11-22 05:34:52 Age [y:d:h:m:s]: 00:044:20:52:16
Block: 1417457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32136 RingCT/type: yes/0
Extra: 015c756fe282709ff0f484ac91e00488fd87b1cbe8e65168cdee3b1b9bbabf2d9902110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9224f9ac9df759c452b79ce91b367e707461ebf7c1a629ef36862d4ebad86c14 0.600000000000 1905980 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": 1417467, "vin": [ { "gen": { "height": 1417457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9224f9ac9df759c452b79ce91b367e707461ebf7c1a629ef36862d4ebad86c14" } } ], "extra": [ 1, 92, 117, 111, 226, 130, 112, 159, 240, 244, 132, 172, 145, 224, 4, 136, 253, 135, 177, 203, 232, 230, 81, 104, 205, 238, 59, 27, 155, 186, 191, 45, 153, 2, 17, 0, 0, 0, 5, 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