← previous blocknext block →recent activity
Analyzing
Block #98,775,510
24 transactions · 22 stateful · 2026-08-24 13:57:00 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,775,510 · 24 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
1w06w07w18w29w110w211w314w015w121w022w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x4387ba94…e195
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x365c6d7d…67fb
0x34b655…2a6f
6 touches
3 conflicts
0xfaddd63e…0b93
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
3 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity