← previous blocknext block →recent activity
Analyzing
Block #86,633,471
40 transactions · 35 stateful · 2026-07-09 13:37:20 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.68
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,633,471 · 40 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w110w211w012w113w214w315w416w017w419w520w521w624w225w126w327w432w533w734w836w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
10 touches
10 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
8 touches
6 conflicts
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity