← previous blocknext block →recent activity
Analyzing
Block #99,156,013
21 transactions · 17 stateful · 2026-08-25 21:58:17 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,156,013 · 21 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
1w02w13w24w35w07w010w011w115w416w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xfa09be5a…1e79
0x34b655…2a6f
4 touches
1 conflict
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity