← previous blocknext block →recent activity
Analyzing
Block #98,779,916
30 transactions · 26 stateful · 2026-08-24 14:19:10 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,779,916 · 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
1w03w04w15w26w07w18w210w011w012w113w214w316w317w421w323w126w229w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xadce6355…03bf
0xa6afd3…d132
6 touches
3 conflicts
0x6e3e9f18…f684
0x34b655…2a6f
4 touches
1 conflict
0x72f046e0…ed7d
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity