← previous blocknext block →recent activity
Analyzing
Block #99,284,226
46 transactions · 42 stateful · 2026-08-26 08:43:24 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
2.26
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #99,284,226 · 46 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
2w04w05w06w18w19w010w111w212w313w419w520w621w623w137w738w839w940w1041w1143w1344w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x5c455afd…ce06
0x34b655…2a6f
12 touches
15 conflicts
0xf4b2a427…0234
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd4305f3b…7f3e
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity