← previous blocknext block →recent activity
Analyzing
Block #99,852,924
23 transactions · 19 stateful · 2026-08-28 08:39:10 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,852,924 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w29w010w111w212w115w316w017w420w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cf31547…051b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3a3976ee…69a8
0x34b655…2a6f
4 touches
1 conflict
0x4d03ec67…d767
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 0x3cf315478f…41051b
Audit this contract →
← previous block·next block →recent activity