← previous blocknext block →recent activity
Analyzing
Block #87,707,542
40 transactions · 28 stateful · 2026-07-14 13:19:34 UTC
Parallelism
92/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,707,542 · 40 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w111w013w014w116w124w025w126w228w129w032w138w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1a625412…648b
0x34b655…2a6f
4 touches
1 conflict
0x2cd98078…527c
0x34b655…2a6f
4 touches
1 conflict
0x35916847…70f2
0x34b655…2a6f
4 touches
1 conflict
0x3eeca510…5146
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity