← previous blocknext block →recent activity
Analyzing
Block #89,750,349
6 transactions · 6 stateful · 2026-07-23 22:28:29 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,750,349 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0xfc3d5171…8357
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0a3dfe51…3b76
0x34b655…2a6f
2 touches
0 conflicts
0x0a3dfe51…3b77
0x34b655…2a6f
2 touches
0 conflicts
0x20dafa3c…372f
0x34b655…2a6f
2 touches
0 conflicts
0x285a5b9b…0160
0x34b655…2a6f
2 touches
0 conflicts
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 0xb9b077a82b…59e029
Audit this contract →
← previous block·next block →recent activity