← previous blocknext block →recent activity
Analyzing
Block #99,200,831
14 transactions · 14 stateful · 2026-08-26 01:43:46 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,200,831 · 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
1w02w13w27w08w110w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bcdd4a1…3d3a
0x34b655…2a6f
6 touches
3 conflicts
0x34baa159…f6a3
0x34b655…2a6f
6 touches
3 conflicts
0x3f798539…99c4
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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 0x2bcdd4a12e…6b3d3a
Audit this contract →
← previous block·next block →recent activity