← previous blocknext block →recent activity
Analyzing
Block #99,161,067
21 transactions · 21 stateful · 2026-08-25 22:23:42 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,161,067 · 21 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
1w04w05w17w08w19w210w311w012w113w214w315w416w519w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b67f6cf…0aab
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xb0e7d9d2…09b2
0x065c9d…c394
6 touches
3 conflicts
0x34bc92c6…d788
0x34b655…2a6f
6 touches
3 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x68531239…e9a3
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x7b67f6cf4c…280aab
Audit this contract →
← previous block·next block →recent activity