← previous blocknext block →recent activity
Analyzing
Block #99,488,506
24 transactions · 23 stateful · 2026-08-27 01:51:53 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,488,506 · 24 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
6w07w18w19w210w313w015w116w419w022w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7be22b96…7be5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x059e0ac0…0267
0x34b655…2a6f
6 touches
3 conflicts
0x4b5f2081…f3c5
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
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 0x7be22b960e…367be5
Audit this contract →
← previous block·next block →recent activity