← previous blocknext block →recent activity
Analyzing
Block #85,990,891
13 transactions · 11 stateful · 2026-07-06 14:03:43 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,990,891 · 13 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
1w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x178db37f…debb
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0xd90a674b…29f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1481f73c…84d2
0x34b655…2a6f
2 touches
0 conflicts
0x1886f544…c8e6
0x34b655…2a6f
2 touches
0 conflicts
0x1c8a3a66…2a9c
0x34b655…2a6f
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 0x39cc218566…27cacb
Audit this contract →
← previous block·next block →recent activity