← previous blocknext block →recent activity
Analyzing
Block #86,850,234
27 transactions · 20 stateful · 2026-07-10 13:46:35 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,850,234 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w110w213w114w315w017w118w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xea83a1f2…18ce
0x34b655…2a6f
5 touches
3 conflicts
0x39c051d9…0418
0x34b655…2a6f
4 touches
1 conflict
0x69e56741…cfa4
0x34b655…2a6f
4 touches
1 conflict
0x7e50ea3a…cdee
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
3 conflicts on slot 0x63c900f479…962600
Audit this contract →
← previous block·next block →recent activity