Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e798b35fe2a90b602de983a5d8b3fbd53f3dc5619161b89a466e8e52c406cb64

Tx prefix hash: 5a616f0f773a1b4268e42117bd8530fb621087a4008e2aaf9d5d5021bee54a6d
Tx public key: 39dd9e75c7fe146a8a9b672ed039ac538cb8a611917179833b17de01e589dae4
Timestamp: 1727021539 Timestamp [UCT]: 2024-09-22 16:12:19 Age [y:d:h:m:s]: 00:262:22:40:51
Block: 1115770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187741 RingCT/type: yes/0
Extra: 0139dd9e75c7fe146a8a9b672ed039ac538cb8a611917179833b17de01e589dae4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e27dbac35136a921a6958133ecf4993ad258dea86f43b3a23cc86aa7b6aa25d 0.600000000000 1596019 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": 1115780, "vin": [ { "gen": { "height": 1115770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e27dbac35136a921a6958133ecf4993ad258dea86f43b3a23cc86aa7b6aa25d" } } ], "extra": [ 1, 57, 221, 158, 117, 199, 254, 20, 106, 138, 155, 103, 46, 208, 57, 172, 83, 140, 184, 166, 17, 145, 113, 121, 131, 59, 23, 222, 1, 229, 137, 218, 228, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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