← previous blocknext block →recent activity
Analyzing
Block #87,690,817
21 transactions · 19 stateful · 2026-07-14 11:27:29 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,690,817 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w110w111w213w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49f75237…44f4
0x34b655…2a6f
4 touches
1 conflict
0x4f51d069…d0b4
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity