← previous blocknext block →recent activity
Analyzing
Block #85,846,961
8 transactions · 8 stateful · 2026-07-05 22:04:06 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,846,961 · 8 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9092da13…341b
0x34b655…2a6f
3 touches
1 conflict
0xa7396f51…7f2f
0x34b655…2a6f
3 touches
1 conflict
0x2148d664…e4c5
0x34b655…2a6f
2 touches
0 conflicts
0x26c9c9b3…b62f
0x34b655…2a6f
2 touches
0 conflicts
0x31955e90…1cef
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
6 conflicts on slot 0xd99b3b6441…7a1c95
Audit this contract →
← previous block·next block →recent activity