← previous blocknext block →recent activity
Analyzing
Block #98,676,361
24 transactions · 15 stateful · 2026-08-24 05:34:22 UTC
Parallelism
88/100
Blocked
47%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,676,361 · 24 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
4w05w06w19w010w011w112w214w115w219w020w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x648d9051…ab81
0xd32edf…ff58
5 touches
3 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
4 touches
1 conflict
0x661638b4…15e9
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity