← previous blocknext block →recent activity
Analyzing
Block #99,935,320
20 transactions · 20 stateful · 2026-08-28 15:34:31 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,935,320 · 20 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
1w03w04w05w07w08w19w210w311w413w114w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3c0e27d…456d
0x34b655…2a6f
8 touches
6 conflicts
0x470b41f6…fc68
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0xaa6fb6df…bc5d
0x34b655…2a6f
8 touches
6 conflicts
0x6324ccc9…14fd
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
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 0xe3c0e27d8e…7b456d
Audit this contract →
← previous block·next block →recent activity