← previous blocknext block →recent activity
Analyzing
Block #99,076,248
35 transactions · 24 stateful · 2026-08-25 15:16:32 UTC
Parallelism
89/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,076,248 · 35 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
3w04w06w011w013w115w216w218w019w120w321w324w025w026w128w129w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad4e90b…33a5
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x0b3eb43a…ca08
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4f7d1ff4…36e3
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xbad4e90ba6…2233a5
Audit this contract →
← previous block·next block →recent activity