← previous blocknext block →recent activity
Analyzing
Block #99,454,598
17 transactions · 17 stateful · 2026-08-26 23:01:07 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,454,598 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w19w210w311w212w113w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x4387ba94…e195
0x34b655…2a6f
8 touches
6 conflicts
0x1bf239bd…46ad
0x34b655…2a6f
6 touches
3 conflicts
0x73cecb0c…2a53
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xad80ed3d…c92a
0x34b655…2a6f
4 touches
1 conflict
0xc3935765…a58e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity