← previous blocknext block →recent activity
Analyzing
Block #98,733,619
27 transactions · 21 stateful · 2026-08-24 10:26:08 UTC
Parallelism
89/100
Blocked
43%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,733,619 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w19w011w012w115w116w220w121w123w024w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58fb4cd2…ef29
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x482471ad…122f
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 0x58fb4cd2e2…30ef29
Audit this contract →
← previous block·next block →recent activity