← previous blocknext block →recent activity
Analyzing
Block #87,726,503
22 transactions · 19 stateful · 2026-07-14 15:26:35 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,726,503 · 22 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
2w03w14w25w09w114w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
6 touches
3 conflicts
0xd74537d8…1675
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 0xc4de665222…6513f4
Audit this contract →
← previous block·next block →recent activity