← previous blocknext block →recent activity
Analyzing
Block #99,204,095
22 transactions · 21 stateful · 2026-08-26 02:00:11 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,204,095 · 22 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
2w03w04w16w09w010w111w112w216w317w018w119w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2f74f175…9289
0x2b46c0…1669
4 touches
1 conflict
0xf17982ba…359a
0x2b46c0…1669
4 touches
1 conflict
0x07a7615d…fc08
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x2c1c2f24…7580
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 0x2202504ef1…9ffad0
Audit this contract →
← previous block·next block →recent activity