← previous blocknext block →recent activity
Analyzing
Block #86,944,621
40 transactions · 35 stateful · 2026-07-11 00:17:37 UTC
Parallelism
60/100
Blocked
77%
Avg conflicts / tx
2.15
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,944,621 · 40 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w08w110w011w112w213w314w415w516w617w721w122w324w225w327w228w429w433w1038w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 conflicts
0xc7a15219…7745
0xa6afd3…d132
8 touches
6 conflicts
0x60c7217a…8c94
0x34b655…2a6f
8 touches
6 conflicts
0x12573732…e891
0x34b655…2a6f
8 touches
6 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity