← previous blocknext block →recent activity
Analyzing
Block #86,948,047
20 transactions · 18 stateful · 2026-07-11 00:40:28 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,948,047 · 20 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
1w02w15w06w17w08w114w215w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0446875…2b96
0x34b655…2a6f
8 touches
6 conflicts
0xf03bae24…db39
0x34b655…2a6f
6 touches
3 conflicts
0x542f415b…3eb1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0xb06917e8…6985
0x34b655…2a6f
6 touches
3 conflicts
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0xb04468752d…352b96
Audit this contract →
← previous block·next block →recent activity