Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d149d1793ca3b59819a4c03d47159cea5b385b1fdba7a81e59501381b92aa36d

Tx prefix hash: 9820999475c8d88b4b506bbe4875be27738a8eb1343f266d0ed8915b8b5d08fe
Tx public key: df805ca41ecbf7ea2b9187c18896414e9d946a953b27d9a4b332252dc22cfc3b
Timestamp: 1727690430 Timestamp [UCT]: 2024-09-30 10:00:30 Age [y:d:h:m:s]: 00:114:09:08:06
Block: 1121315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81732 RingCT/type: yes/0
Extra: 01df805ca41ecbf7ea2b9187c18896414e9d946a953b27d9a4b332252dc22cfc3b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c941ea3c062cd1f55b2f8acc87cbd479f47b3c7dfff9e7d3cb47f8104e2ffb4 0.600000000000 1603546 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": 1121325, "vin": [ { "gen": { "height": 1121315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c941ea3c062cd1f55b2f8acc87cbd479f47b3c7dfff9e7d3cb47f8104e2ffb4" } } ], "extra": [ 1, 223, 128, 92, 164, 30, 203, 247, 234, 43, 145, 135, 193, 136, 150, 65, 78, 157, 148, 106, 149, 59, 39, 217, 164, 179, 50, 37, 45, 194, 44, 252, 59, 2, 17, 0, 0, 0, 9, 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