← previous blocknext block →recent activity
Analyzing
Block #86,755,850
23 transactions · 21 stateful · 2026-07-10 03:15:59 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,755,850 · 23 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
2w04w05w16w011w112w213w314w115w418w119w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa468c950…4db2
0x34b655…2a6f
6 touches
3 conflicts
0x365bd58a…0eb5
0x34b655…2a6f
6 touches
3 conflicts
0x88692611…d222
0x34b655…2a6f
6 touches
3 conflicts
0xc3688185…9b36
0x34b655…2a6f
6 touches
3 conflicts
0xc788862c…c259
0x34b655…2a6f
6 touches
3 conflicts
0xe8f5ee5e…bc54
0x34b655…2a6f
6 touches
3 conflicts
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