← previous blocknext block →recent activity
Analyzing
Block #86,794,021
20 transactions · 17 stateful · 2026-07-10 07:30:41 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,794,021 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w08w29w110w312w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0x05435a4a…0c07
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1d
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1e
0x34b655…2a6f
4 touches
1 conflict
0xaef1516c…0858
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