← previous blocknext block →recent activity
Analyzing
Block #87,642,768
17 transactions · 14 stateful · 2026-07-14 06:06:25 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,642,768 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w210w312w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xe6df4062…2966
0x34b655…2a6f
10 touches
10 conflicts
0x05975727…7fcf
0x34b655…2a6f
6 touches
3 conflicts
0x38e39eef…50bd
0x34b655…2a6f
6 touches
3 conflicts
0x91ace65b…97af
0x34b655…2a6f
4 touches
1 conflict
0x98459f89…575d
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity