← previous blocknext block →recent activity
Analyzing
Block #86,883,605
23 transactions · 19 stateful · 2026-07-10 17:29:51 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,883,605 · 23 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
1w010w011w112w113w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x21683d77…4e07
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x82e3f65a…d23c
0x34b655…2a6f
6 touches
3 conflicts
0x6fa48528…fdbd
0x34b655…2a6f
6 touches
3 conflicts
0xc8024fac…da0b
0x34b655…2a6f
6 touches
3 conflicts
0xc8024fac…da0a
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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