← previous blocknext block →recent activity
Analyzing
Block #85,991,846
22 transactions · 19 stateful · 2026-07-06 14:10:06 UTC
Parallelism
64/100
Blocked
37%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,991,846 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w014w015w116w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xe87fb2d3…fc07
0x34b655…2a6f
6 touches
3 conflicts
0x1ced2a7d…5c90
0x34b655…2a6f
4 touches
1 conflict
0x1de1cbec…73ca
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2c506459…5351
0x34b655…2a6f
4 touches
1 conflict
0x309ef367…e8a1
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity