← previous blocknext block →recent activity
Analyzing
Block #86,501,299
18 transactions · 16 stateful · 2026-07-08 22:52:26 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,501,299 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w616w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0xe727ab72…768b
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x23778a1f…dec4
0x34b655…2a6f
6 touches
3 conflicts
0xebd8c9b0…2ba6
0x34b655…2a6f
6 touches
3 conflicts
0x3f6effa8…e2e4
0x34b655…2a6f
6 touches
3 conflicts
0x6b9ca80e…cce8
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity