← previous blocknext block →recent activity
Analyzing
Block #98,779,405
30 transactions · 26 stateful · 2026-08-24 14:16:36 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,779,405 · 30 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
1w04w15w06w18w29w011w115w216w017w119w223w225w328w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xbc5d509c…a2a2
0xd32edf…ff58
5 touches
3 conflicts
0x42522e76…2593
0x34b655…2a6f
4 touches
1 conflict
0x9116c17c…e222
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity