← previous blocknext block →recent activity
Analyzing
Block #98,650,804
22 transactions · 20 stateful · 2026-08-24 03:21:04 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,650,804 · 22 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
1w03w15w07w18w010w212w113w315w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x71717491…10cf
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x92e91db9…0518
0x34b655…2a6f
4 touches
1 conflict
0xc5f4529d…63e6
0xa6afd3…d132
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 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity