← previous blocknext block →recent activity
Analyzing
Block #85,972,127
28 transactions · 25 stateful · 2026-07-06 11:58:15 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,972,127 · 28 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
5w07w010w011w113w014w115w116w117w120w224w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd90a674b…29f7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x6cda3f80…809b
0x34b655…2a6f
4 touches
1 conflict
0x8c84e7fe…afbd
0x34b655…2a6f
4 touches
1 conflict
0x98834cc0…6c23
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
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 0xd90a674bde…9a29f7
Audit this contract →
← previous block·next block →recent activity