← previous blocknext block →recent activity
Analyzing
Block #98,848,161
34 transactions · 27 stateful · 2026-08-24 20:02:44 UTC
Parallelism
91/100
Blocked
37%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,848,161 · 34 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w010w011w113w014w117w018w122w023w226w127w228w131w232w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x659bd0…a9da
6 touches
3 conflicts
0x7e28e55c…d05c
0x754704…b603
6 touches
3 conflicts
0x00000000…0001
0x659bd0…a9da
6 touches
3 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x4b300c19…7c01
0xd32edf…ff58
5 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xeea3f128…72db
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: 0x659bd0bc…d4a9da
3 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity