← previous blocknext block →recent activity
Analyzing
Block #86,695,228
17 transactions · 12 stateful · 2026-07-09 20:30:54 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,695,228 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w213w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
6 touches
3 conflicts
0x12573732…e891
0x34b655…2a6f
4 touches
1 conflict
0x1535d171…c68b
0x34b655…2a6f
4 touches
1 conflict
0x19840da5…08b8
0x34b655…2a6f
4 touches
1 conflict
0x1e274565…363d
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity