← previous blocknext block →recent activity
Analyzing
Block #98,737,152
24 transactions · 18 stateful · 2026-08-24 10:43:54 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,737,152 · 24 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
1w03w04w15w06w17w28w010w011w112w318w419w520w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa2b16f3f…0d71
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x2290912b…2613
0x34b655…2a6f
4 touches
1 conflict
0x45885570…ed97
0x34b655…2a6f
4 touches
1 conflict
0x67088d1d…dcd6
0x34b655…2a6f
4 touches
1 conflict
0x68292fe7…d918
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 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity