← previous blocknext block →recent activity
Analyzing
Block #86,714,755
14 transactions · 7 stateful · 2026-07-09 22:41:14 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,714,755 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xadd2210b…9e29
0x34b655…2a6f
4 touches
1 conflict
0xdbf50b38…ac8c
0x34b655…2a6f
4 touches
1 conflict
0xde9bb8b7…ac39
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity