← previous blocknext block →recent activity
Analyzing
Block #86,931,218
14 transactions · 11 stateful · 2026-07-10 22:48:02 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,931,218 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba559de1…6d2c
0x34b655…2a6f
6 touches
3 conflicts
0x552ac70a…d74b
0x34b655…2a6f
4 touches
1 conflict
0x5b813b1d…5968
0x34b655…2a6f
4 touches
1 conflict
0x0960ac51…5440
0x34b655…2a6f
4 touches
1 conflict
0xb5c1ae56…437a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa0acdcf7…bd86
0x34b655…2a6f
4 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
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
3 conflicts on slot 0xba559de17c…336d2c
Audit this contract →
← previous block·next block →recent activity