← previous blocknext block →recent activity
Analyzing
Block #99,956,871
14 transactions · 13 stateful · 2026-08-28 17:23:08 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,956,871 · 14 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
1w02w14w06w07w19w210w011w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x844b7221…5ad8
0x34b655…2a6f
6 touches
3 conflicts
0xf5454ebd…4451
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x27b6010e…e4aa
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 0x844b7221ee…b65ad8
Audit this contract →
← previous block·next block →recent activity