← previous blocknext block →recent activity
Analyzing
Block #99,452,013
21 transactions · 17 stateful · 2026-08-26 22:48:07 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,452,013 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w110w212w013w014w115w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f0917b…1d10
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0xa031f4a8…3fad
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
3 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity