← previous blocknext block →recent activity
Analyzing
Block #89,572,926
18 transactions · 18 stateful · 2026-07-23 05:15:20 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,572,926 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w09w310w411w115w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1cc9519…84c1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8b28956a…3b73
0x34b655…2a6f
6 touches
3 conflicts
0x419cbce1…3d2d
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9cf61590…ad8c
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
10 conflicts on slot 0xf1cc9519e3…fe84c1
Audit this contract →
← previous block·next block →recent activity