← previous blocknext block →recent activity
Analyzing
Block #89,403,228
10 transactions · 9 stateful · 2026-07-22 10:21:36 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,403,228 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x55cd082c…d073
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e32
0x34b655…2a6f
4 touches
1 conflict
0x9f4bc324…e6a6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0xf58eb4e0…6b86
0x34b655…2a6f
4 touches
1 conflict
0xf86f8100…072f
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: Perpl
1 conflict on slot 0x54f7f60f23…cb43cc
Audit this contract →
← previous block·next block →recent activity