← previous blocknext block →recent activity
Analyzing
Block #86,699,134
16 transactions · 14 stateful · 2026-07-09 20:56:58 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,699,134 · 16 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
1w02w13w04w16w27w38w413w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x0a5c6e05…a29a
0x34b655…2a6f
4 touches
1 conflict
0x120933a6…dbe3
0x34b655…2a6f
4 touches
1 conflict
0x32bd9527…5616
0x34b655…2a6f
4 touches
1 conflict
0x3e56ba2d…6713
0x34b655…2a6f
4 touches
1 conflict
0x5c8d9778…572f
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity