← previous blocknext block →recent activity
Analyzing
Block #89,760,014
18 transactions · 16 stateful · 2026-07-23 23:17:14 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,760,014 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w19w110w211w212w313w314w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
12 touches
15 conflicts
0x92339d95…0800
0x0000a8…8888
10 touches
10 conflicts
0xe52a5e77…41a4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0xa8590d68…d5c8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xb1c8ead4…c38888
15 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity