← previous blocknext block →recent activity
Analyzing
Block #86,829,156
15 transactions · 12 stateful · 2026-07-10 11:25:44 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,829,156 · 15 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
2w03w04w16w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x947a5a30…bd4b
0x34b655…2a6f
8 touches
6 conflicts
0x079017cd…e5a7
0x34b655…2a6f
6 touches
3 conflicts
0x88413c1a…7783
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x44231245…5442
0x34b655…2a6f
4 touches
1 conflict
0x460eb444…fa7e
0x34b655…2a6f
4 touches
1 conflict
0x68edd6ac…8c3c
0x34b655…2a6f
4 touches
1 conflict
0x7c7eff13…16db
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 0x947a5a30aa…93bd4b
Audit this contract →
← previous block·next block →recent activity