← previous blocknext block →recent activity
Analyzing
Block #98,767,105
21 transactions · 21 stateful · 2026-08-24 13:14:43 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,767,105 · 21 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
1w02w14w05w18w211w112w013w114w217w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51dc
0x69a5f9…2fef
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity