← previous blocknext block →recent activity
Analyzing
Block #86,914,133
13 transactions · 12 stateful · 2026-07-10 20:53:52 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,914,133 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0x5d106d2b…c35e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
4 touches
1 conflict
0x2acd406f…1f22
0x34b655…2a6f
4 touches
1 conflict
0x2d12e250…0970
0x34b655…2a6f
4 touches
1 conflict
0x57e0b825…eb63
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0xa42e848215…53b88f
Audit this contract →
← previous block·next block →recent activity