← previous blocknext block →recent activity
Analyzing
Block #86,756,475
22 transactions · 22 stateful · 2026-07-10 03:20:09 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,756,475 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w210w013w115w016w119w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc788862c…c259
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0xe8377f79…5f5e
0x34b655…2a6f
6 touches
3 conflicts
0xee5a28ec…7261
0x34b655…2a6f
6 touches
3 conflicts
0xefcaccf2…c083
0x34b655…2a6f
6 touches
3 conflicts
0xf806218e…c4da
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfcdb5918…2b49
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 0xc788862c2e…6ec259
Audit this contract →
← previous block·next block →recent activity