← previous blocknext block →recent activity
Analyzing
Block #86,804,261
16 transactions · 13 stateful · 2026-07-10 08:39:09 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,804,261 · 16 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
1w02w03w14w05w17w18w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55642f63…03d6
0x34b655…2a6f
6 touches
3 conflicts
0xdfc58aa8…e1df
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x194be77e…58ae
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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
3 conflicts on slot 0x55642f6368…8e03d6
Audit this contract →
← previous block·next block →recent activity