← previous blocknext block →recent activity
Analyzing
Block #86,954,882
18 transactions · 17 stateful · 2026-07-11 01:26:08 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,954,882 · 18 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
2w03w14w05w16w210w211w313w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
0x34b655…2a6f
4 touches
1 conflict
0x4740ce34…74c6
0x34b655…2a6f
4 touches
1 conflict
0x60d7fd08…a37e
0x34b655…2a6f
4 touches
1 conflict
0x636fd21a…9978
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity