← previous blocknext block →recent activity
Analyzing
Block #99,623,626
30 transactions · 28 stateful · 2026-08-27 13:18:49 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,623,626 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w28w110w111w012w013w114w015w117w318w221w424w229w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x8450a61d…e094
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6fce7a05…d778
0x34b655…2a6f
8 touches
6 conflicts
0xf7a94262…e293
0x34b655…2a6f
7 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
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 0x6d5d1fb525…a986a7
Audit this contract →
← previous block·next block →recent activity