← previous blocknext block →recent activity
Analyzing
Block #86,850,925
24 transactions · 13 stateful · 2026-07-10 13:51:11 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,850,925 · 24 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
4w05w16w28w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1a7d77fe…f01a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x565f28e7…6746
0x34b655…2a6f
4 touches
1 conflict
0xaa10bb38…e655
0x34b655…2a6f
4 touches
1 conflict
0xb7b8bfda…efc0
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity