← previous blocknext block →recent activity
Analyzing
Block #85,928,887
23 transactions · 19 stateful · 2026-07-06 07:09:48 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,928,887 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w011w117w118w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xa4dae615…1cf8
0x34b655…2a6f
6 touches
3 conflicts
0xcbd23469…a4df
0x34b655…2a6f
6 touches
3 conflicts
0x08d66073…e706
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity