← previous blocknext block →recent activity
Analyzing
Block #86,656,832
16 transactions · 11 stateful · 2026-07-09 16:14:41 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,656,832 · 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
1w03w04w16w07w28w39w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x342f88f5…2a06
0x34b655…2a6f
4 touches
1 conflict
0x42aad825…b067
0x34b655…2a6f
4 touches
1 conflict
0x5d9e33b1…3524
0x34b655…2a6f
4 touches
1 conflict
0x6777440a…afd6
0x34b655…2a6f
4 touches
1 conflict
0x71ac14a2…6760
0x34b655…2a6f
4 touches
1 conflict
0x71ac14a2…6761
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity