← previous blocknext block →recent activity
Analyzing
Block #86,771,231
14 transactions · 8 stateful · 2026-07-10 04:58:40 UTC
Parallelism
86/100
Blocked
13%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,771,231 · 14 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
6w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5187f0d7…36a9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180d
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180e
0x34b655…2a6f
4 touches
1 conflict
0x9cbe5c47…424b
0x34b655…2a6f
4 touches
1 conflict
0xc40c8e2b…b832
0x34b655…2a6f
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
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 0x5187f0d7dc…a636a9
Audit this contract →
← previous block·next block →recent activity