← previous blocknext block →recent activity
Analyzing
Block #98,505,701
35 transactions · 28 stateful · 2026-08-23 14:44:49 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,505,701 · 35 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
1w02w03w19w010w112w016w017w218w122w323w424w525w327w128w030w131w233w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x81ceb686…4df3
0x34b655…2a6f
6 touches
3 conflicts
0xb77dc863…dd3d
0x34b655…2a6f
4 touches
1 conflict
0xe22455da…1ce1
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity