← previous blocknext block →recent activity
Analyzing
Block #98,851,112
26 transactions · 23 stateful · 2026-08-24 20:17:35 UTC
Parallelism
85/100
Blocked
57%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,851,112 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w29w314w215w316w218w019w120w221w323w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x35306d0d…252f
0xd32edf…ff58
7 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51dc
0x69a5f9…2fef
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
6 touches
3 conflicts
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
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