← previous blocknext block →recent activity
Analyzing
Block #87,879,186
21 transactions · 17 stateful · 2026-07-15 08:27:52 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,879,186 · 21 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
1w06w010w111w012w113w214w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a058c6…74a1
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x4940bb84…4ec2
0x34b655…2a6f
4 touches
1 conflict
0x4e782273…1690
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a2
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 0x64a058c6c8…5774a1
Audit this contract →
← previous block·next block →recent activity