← previous blocknext block →recent activity
Analyzing
Block #86,827,721
21 transactions · 20 stateful · 2026-07-10 11:16:09 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,827,721 · 21 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
1w02w17w28w09w111w012w213w114w115w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3237bef6…f95e
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x17c44db3…8888
0xa6afd3…d132
6 touches
3 conflicts
0x4d6cbc23…1000
0xd32edf…ff58
5 touches
3 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
4 touches
1 conflict
0x350a4ec3…783e
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
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 0x3237bef6c1…83f95e
Audit this contract →
← previous block·next block →recent activity