← previous blocknext block →recent activity
Analyzing
Block #98,644,265
30 transactions · 22 stateful · 2026-08-24 02:47:05 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,644,265 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w28w09w112w013w116w218w019w120w322w324w125w326w427w028w129w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xd97b0449…00a0
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x1408e7c7…f324
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
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
10 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity