← previous blocknext block →recent activity
Analyzing
Block #87,732,765
22 transactions · 19 stateful · 2026-07-14 16:08:29 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,732,765 · 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
1w02w13w24w38w09w111w012w116w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x80fd3987…2314
0x34b655…2a6f
8 touches
6 conflicts
0x34b73c43…1fb1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x24e3bf88…17bf
0x34b655…2a6f
6 touches
3 conflicts
0x36b8bd62…0beb
0x34b655…2a6f
6 touches
3 conflicts
0x64a058c6…74a1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity