← previous blocknext block →recent activity
Analyzing
Block #98,596,829
25 transactions · 23 stateful · 2026-08-23 22:40:23 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,596,829 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w29w010w111w212w013w115w018w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x48ed1159…abe9
0x2b46c0…1669
4 touches
1 conflict
0x0e18d182…0425
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 0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block·next block →recent activity