Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75c1c13d6af194fda92e428f956b19041b2ac6c3b910f8920f4de3209b92e9c

Tx prefix hash: b9e0f7158dd8f2e7f9b7f9e7d5b2ac840668bd859ce93469265b2bdf5736fb5b
Tx public key: 35a718449cce4c7292265b995fada605e45012ddf97ab67598c1e23c2f33c5e3
Timestamp: 1699443314 Timestamp [UCT]: 2023-11-08 11:35:14 Age [y:d:h:m:s]: 01:187:06:28:45
Block: 887135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395060 RingCT/type: yes/0
Extra: 0135a718449cce4c7292265b995fada605e45012ddf97ab67598c1e23c2f33c5e30211000000064b8f5122000000000000000000

1 output(s) for total of 0.705591727000 dcy

stealth address amount amount idx
00: 230876d196029f3d382d1321abbf1e91b0fcf8367f4076f6c50e0d7b4a1b78f4 0.705591727000 1342992 of 0

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": 887145, "vin": [ { "gen": { "height": 887135 } } ], "vout": [ { "amount": 705591727, "target": { "key": "230876d196029f3d382d1321abbf1e91b0fcf8367f4076f6c50e0d7b4a1b78f4" } } ], "extra": [ 1, 53, 167, 24, 68, 156, 206, 76, 114, 146, 38, 91, 153, 95, 173, 166, 5, 228, 80, 18, 221, 249, 122, 182, 117, 152, 193, 226, 60, 47, 51, 197, 227, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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