← previous blocknext block →recent activity
Analyzing
Block #89,380,237
13 transactions · 13 stateful · 2026-07-22 07:47:52 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,380,237 · 13 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
1w02w03w14w15w26w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6323c5ea…ce8a
0x34b655…2a6f
6 touches
3 conflicts
0x840db28a…b65b
0x34b655…2a6f
6 touches
3 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x6f46250b…3bf2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity