← previous blocknext block →recent activity
Analyzing
Block #85,972,167
18 transactions · 14 stateful · 2026-07-06 11:58:31 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,972,167 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54b193ad…c830
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd90a674b…29f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xee25bf8b…bda7
0xd32edf…ff58
3 touches
1 conflict
0x9ee4db5a…a893
0x065c9d…c394
2 touches
0 conflicts
0xa2bf5f43…387a
0x065c9d…c394
2 touches
0 conflicts
0xa8dd842b…f6d6
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x54b193ad55…f5c830
Audit this contract →
← previous block·next block →recent activity