← previous blocknext block →recent activity
Analyzing
Block #99,488,728
19 transactions · 19 stateful · 2026-08-27 01:53:00 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,488,728 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w210w011w212w115w216w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059e0ac0…0267
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x91913ff0…97f8
0x34b655…2a6f
6 touches
3 conflicts
0xf4b2a427…0234
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
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 0x059e0ac09d…0f0267
Audit this contract →
← previous block·next block →recent activity