← previous blocknext block →recent activity
Analyzing
Block #88,367,073
58 transactions · 42 stateful · 2026-07-17 14:52:39 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
1.6
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #88,367,073 · 58 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w08w116w017w119w020w121w222w323w424w527w628w731w132w234w836w337w138w240w445w947w1056w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0x61377ba1…0bef
0xa6afd3…d132
8 touches
6 conflicts
0x43cdca8f…780d
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity