← previous blocknext block →recent activity
Analyzing
Block #87,714,103
29 transactions · 22 stateful · 2026-07-14 14:03:30 UTC
Parallelism
90/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,714,103 · 29 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
2w05w08w114w015w116w218w019w220w121w124w226w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe0b11326…d277
0xd32edf…ff58
5 touches
3 conflicts
0x64800813…db9f
0x34b655…2a6f
4 touches
1 conflict
0x86d1a3fb…ed61
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb5c1ae56…437a
0x34b655…2a6f
4 touches
1 conflict
0xc0fb0790…a482
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity