← previous blocknext block →recent activity
Analyzing
Block #99,869,959
23 transactions · 22 stateful · 2026-08-28 10:05:09 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,869,959 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w07w18w19w210w111w212w014w216w319w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf61f287…3f4e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6098b25a…79dd
0x34b655…2a6f
4 touches
1 conflict
0x76bf3072…d950
0x34b655…2a6f
4 touches
1 conflict
0x7d63d93a…1188
0x34b655…2a6f
4 touches
1 conflict
0x90fa3fa2…3879
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 0xcf61f28790…6b3f4e
Audit this contract →
← previous block·next block →recent activity