← previous blocknext block →recent activity
Analyzing
Block #86,914,384
17 transactions · 13 stateful · 2026-07-10 20:55:33 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,914,384 · 17 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
1w02w13w24w35w47w08w110w511w616w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e45018…b59c
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
10 touches
10 conflicts
0x5d7f309d…5145
0x34b655…2a6f
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
10 touches
10 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
10 touches
10 conflicts
0xd4541380…f8d2
0x34b655…2a6f
10 touches
10 conflicts
0xe727ab72…768b
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0xa7e45018ba…2fb59c
Audit this contract →
← previous block·next block →recent activity