← previous blocknext block →recent activity
Analyzing
Block #86,272,704
23 transactions · 22 stateful · 2026-07-07 21:25:09 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,272,704 · 23 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
1w03w16w07w18w211w213w314w015w118w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
6 touches
3 conflicts
0x89750670…2dea
0xa6afd3…d132
6 touches
3 conflicts
0xb81b0e90…6c19
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity