← previous blocknext block →recent activity
Analyzing
Block #99,276,217
40 transactions · 36 stateful · 2026-08-26 08:03:07 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
2.42
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #99,276,217 · 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
5w06w18w09w010w111w212w313w416w118w522w623w724w825w929w130w237w1338w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x5c1b956d…14d3
0x34b655…2a6f
8 touches
6 conflicts
0x248f83d1…63cf
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x33000c0a…82c3
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
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
55 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity