← previous blocknext block →recent activity
Analyzing
Block #98,322,891
25 transactions · 17 stateful · 2026-08-22 23:23:32 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,322,891 · 25 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
2w03w07w08w110w211w112w319w220w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x862699a8…01e6
0x065c9d…c394
5 touches
3 conflicts
0x574d9a38…13a8
0x40c49f…2af0
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 0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block·next block →recent activity