← previous blocknext block →recent activity
Analyzing
Block #86,959,806
16 transactions · 15 stateful · 2026-07-11 01:59:03 UTC
Parallelism
56/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,959,806 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w49w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8620c47a…99dc
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a2
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a3
0x34b655…2a6f
4 touches
1 conflict
0xe1caddba…a708
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity