← previous blocknext block →recent activity
Analyzing
Block #99,353,013
24 transactions · 22 stateful · 2026-08-26 14:29:27 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,353,013 · 24 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
2w03w14w06w07w112w013w114w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9533afa1…2614
0x34b655…2a6f
8 touches
6 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xcfcb6f69…eadb
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x7d7ff6bb…f729
0x34b655…2a6f
4 touches
1 conflict
0x8613478f…2a75
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 0x9533afa186…6a2614
Audit this contract →
← previous block·next block →recent activity