Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba6a747d092baa78d23333571911cf71685e12b5ab4e863e845583d2685e75cb

Tx prefix hash: c318d71a73813852dc3383dcfbe1e0dd652d3e5a5598805be44c7013ca1331dc
Tx public key: 565c74ebb13c33f4ae7b4c1caa09e6b79843f2cbd9ab4930b1051dbc93bdd168
Timestamp: 1709321435 Timestamp [UCT]: 2024-03-01 19:30:35 Age [y:d:h:m:s]: 00:340:22:11:33
Block: 969031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243767 RingCT/type: yes/0
Extra: 01565c74ebb13c33f4ae7b4c1caa09e6b79843f2cbd9ab4930b1051dbc93bdd16802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd0c445efe5ebb4b8182aa28a5c5766ff1d0077327dee06d78e1ddd2a68a6a9 0.600000000000 1428858 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": 969041, "vin": [ { "gen": { "height": 969031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd0c445efe5ebb4b8182aa28a5c5766ff1d0077327dee06d78e1ddd2a68a6a9" } } ], "extra": [ 1, 86, 92, 116, 235, 177, 60, 51, 244, 174, 123, 76, 28, 170, 9, 230, 183, 152, 67, 242, 203, 217, 171, 73, 48, 177, 5, 29, 188, 147, 189, 209, 104, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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