← previous blocknext block →recent activity
Analyzing
Block #86,787,770
13 transactions · 9 stateful · 2026-07-10 06:49:00 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,787,770 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf60062ab…f98c
0x34b655…2a6f
4 touches
1 conflict
0xf60062ab…f98d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0xb4ad3e17…76f4
0x34b655…2a6f
4 touches
1 conflict
0x689257af…460b
0x34b655…2a6f
3 touches
1 conflict
0xc86bbc20…263c
0x40c49f…2af0
2 touches
0 conflicts
0xf36f2d97…43f9
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0xf60062ab4e…aef98c
Audit this contract →
← previous block·next block →recent activity