← previous blocknext block →recent activity
Analyzing
Block #87,724,883
8 transactions · 7 stateful · 2026-07-14 15:15:44 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,724,883 · 8 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
1w03w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x808ff8b4…4450
0x34b655…2a6f
4 touches
1 conflict
0xbdbdafe0…d811
0x34b655…2a6f
4 touches
1 conflict
0xbdbdafe0…d812
0x34b655…2a6f
4 touches
1 conflict
0xcf5ef070…7d4f
0x34b655…2a6f
4 touches
1 conflict
0xd8bc53a3…c2fe
0x34b655…2a6f
4 touches
1 conflict
0xff3170ba…6c44
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