← previous blocknext block →recent activity
Analyzing
Block #98,566,928
38 transactions · 28 stateful · 2026-08-23 20:04:26 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,566,928 · 38 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w110w011w117w018w123w228w029w131w335w236w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36743f6f…476b
0x3bd359…433a
6 touches
3 conflicts
0xe31cf99d…cb66
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3ffcf753…61d0
0xd32edf…ff58
5 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf3981be5…2c47
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: Wrapped MON (WMON)
3 conflicts on slot 0x36743f6fc4…37476b
Audit this contract →
← previous block·next block →recent activity