Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ebc0520ab0772520584212b1a2d5177a7114a978c90d88d3f703b0f8dbc544e

Tx prefix hash: f939f5517df543f2d7edbd77a6fb0a77cbe3eb69b9c0ce35ce6d197fd30721be
Tx public key: 77b789a813f8328169ab1bc4adb1d320d0930116b79b19694bc924c27c0765f5
Timestamp: 1723949938 Timestamp [UCT]: 2024-08-18 02:58:58 Age [y:d:h:m:s]: 00:098:14:28:51
Block: 1090306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70523 RingCT/type: yes/0
Extra: 0177b789a813f8328169ab1bc4adb1d320d0930116b79b19694bc924c27c0765f5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9afba25ce0ad26a83f9de767a4ad55cff3af2c2351d55ab7e6d6793566d84a5 0.600000000000 1564929 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": 1090316, "vin": [ { "gen": { "height": 1090306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9afba25ce0ad26a83f9de767a4ad55cff3af2c2351d55ab7e6d6793566d84a5" } } ], "extra": [ 1, 119, 183, 137, 168, 19, 248, 50, 129, 105, 171, 27, 196, 173, 177, 211, 32, 208, 147, 1, 22, 183, 155, 25, 105, 75, 201, 36, 194, 124, 7, 101, 245, 2, 17, 0, 0, 0, 6, 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