← previous blocknext block →recent activity
Analyzing
Block #86,256,299
24 transactions · 23 stateful · 2026-07-07 19:35:45 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,256,299 · 24 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
2w05w06w17w211w112w314w217w318w420w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
12 touches
15 conflicts
0xb0446875…2b96
0x34b655…2a6f
8 touches
6 conflicts
0x261c40aa…b133
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
6 touches
3 conflicts
0xdec5bfea…d17f
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x781b3625…5312
0x34b655…2a6f
6 touches
3 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
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
15 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity