← previous blocknext block →recent activity
Analyzing
Block #86,771,738
23 transactions · 20 stateful · 2026-07-10 05:02:04 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,771,738 · 23 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
1w02w03w14w25w16w07w18w29w310w114w216w321w022w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x06aed19e…ca57
0x34b655…2a6f
6 touches
3 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
6 touches
3 conflicts
0x1911fbd1…f1bf
0x34b655…2a6f
6 touches
3 conflicts
0x31d2c775…b3b9
0x34b655…2a6f
6 touches
3 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
6 touches
3 conflicts
0x3d4584df…ffed
0x34b655…2a6f
6 touches
3 conflicts
0x567bb003…113a
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity