← previous blocknext block →recent activity
Analyzing
Block #86,828,079
22 transactions · 18 stateful · 2026-07-10 11:18:32 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,828,079 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w19w210w314w216w217w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
8 touches
6 conflicts
0x9068a9bc…86ee
0x34b655…2a6f
6 touches
3 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
6 touches
3 conflicts
0x5104991c…f259
0x34b655…2a6f
6 touches
3 conflicts
0x079017cd…e5a7
0x34b655…2a6f
6 touches
3 conflicts
0xb7a47e62…7963
0x34b655…2a6f
4 touches
1 conflict
0xbca4de0c…577c
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity