← previous blocknext block →recent activity
Analyzing
Block #86,793,962
27 transactions · 18 stateful · 2026-07-10 07:30:17 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,793,962 · 27 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
1w05w08w19w113w214w116w018w120w022w223w325w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x98fd563f…a9fc
0xd32edf…ff58
5 touches
3 conflicts
0x06e8b95a…9ed2
0x34b655…2a6f
4 touches
1 conflict
0x0c4d9965…6182
0x34b655…2a6f
4 touches
1 conflict
0x13c969ed…bc08
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e3
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e4
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity