← previous blocknext block →recent activity
Analyzing
Block #89,741,222
10 transactions · 9 stateful · 2026-07-23 21:42:20 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,741,222 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7e4c78a…f3f6
0x34b655…2a6f
4 touches
1 conflict
0x58d6b9cf…7c9e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x2b819bc5…b52e
0x34b655…2a6f
2 touches
0 conflicts
0x39644a09…0bad
0x34b655…2a6f
2 touches
0 conflicts
0x53142478…5458
0x34b655…2a6f
2 touches
0 conflicts
0x5b2bcb51…dc87
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 0xb7e4c78ab6…fcf3f6
Audit this contract →
← previous block·next block →recent activity