← previous blocknext block →recent activity
Analyzing
Block #89,378,087
14 transactions · 12 stateful · 2026-07-22 07:33:28 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,378,087 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92145e19…6904
0x34b655…2a6f
4 touches
1 conflict
0xee9f03fd…1e57
0x34b655…2a6f
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
2 touches
0 conflicts
0x07ed27ca…3903
0x34b655…2a6f
2 touches
0 conflicts
0x0dd44476…ef40
0x34b655…2a6f
2 touches
0 conflicts
0x1f5dc61b…2471
0x34b655…2a6f
2 touches
0 conflicts
0x324ec4d3…f156
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity