← previous blocknext block →recent activity
Analyzing
Block #89,688,041
9 transactions · 9 stateful · 2026-07-23 17:13:59 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,688,041 · 9 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0x09dddc76…e12a
0x34b655…2a6f
2 touches
0 conflicts
0x0b234df0…aee3
0x34b655…2a6f
2 touches
0 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
2 touches
0 conflicts
0x282fd1fa…1fca
0x34b655…2a6f
2 touches
0 conflicts
0x28c62bca…b746
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity