← previous blocknext block →recent activity
Analyzing
Block #86,945,384
15 transactions · 15 stateful · 2026-07-11 00:22:43 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,945,384 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e303d0b…01bb
0x34b655…2a6f
6 touches
3 conflicts
0x1c0c501c…14b2
0x34b655…2a6f
4 touches
1 conflict
0x230a3fb0…e64c
0x34b655…2a6f
4 touches
1 conflict
0x262e21c1…75fd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b8d2e5…3f2f
0x34b655…2a6f
4 touches
1 conflict
0x68938542…ecbb
0x34b655…2a6f
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
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
3 conflicts on slot 0x6e303d0b67…b801bb
Audit this contract →
← previous block·next block →recent activity