← previous blocknext block →recent activity
Analyzing
Block #89,828,917
20 transactions · 20 stateful · 2026-07-24 05:05:01 UTC
Parallelism
75/100
Blocked
55%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,828,917 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w28w09w110w011w012w113w114w215w316w217w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
10 touches
10 conflicts
0x92339d95…0800
0x0000a8…8888
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd7d3e7dd…2bf3
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x40296dac…6303
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
10 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity