← previous blocknext block →recent activity
Analyzing
Block #99,188,340
13 transactions · 12 stateful · 2026-08-26 00:40:55 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,188,340 · 13 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
2w03w14w25w37w18w29w011w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02373c43…3cb3
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf3b57c2c…7875
0x34b655…2a6f
6 touches
3 conflicts
0xac808a27…82db
0x34b655…2a6f
6 touches
3 conflicts
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
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
6 conflicts on slot 0x02373c432b…ff3cb3
Audit this contract →
← previous block·next block →recent activity