← previous blocknext block →recent activity
Analyzing
Block #86,771,502
10 transactions · 8 stateful · 2026-07-10 05:00:29 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,771,502 · 10 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
2w03w05w17w2
- 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
0xc40c8e2b…b832
0x34b655…2a6f
6 touches
3 conflicts
0xc34f797f…dfaa
0x34b655…2a6f
4 touches
1 conflict
0x356f8a28…5791
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54eb
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54ec
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