← previous blocknext block →recent activity
Analyzing
Block #98,666,770
19 transactions · 14 stateful · 2026-08-24 04:44:26 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,666,770 · 19 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
1w02w13w24w38w411w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36743f6f…476b
0x3bd359…433a
8 touches
6 conflicts
0xe31cf99d…cb66
0x754704…b603
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x0aa822e3…3908
0x065c9d…c394
3 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)
6 conflicts on slot 0x36743f6fc4…37476b
Audit this contract →
← previous block·next block →recent activity