← previous blocknext block →recent activity
Analyzing
Block #98,434,742
34 transactions · 30 stateful · 2026-08-23 08:46:14 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,434,742 · 34 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
1w02w13w24w05w16w07w18w29w310w411w318w019w120w221w025w432w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xba367824…ce94
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x1045386d…cb89
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x41c48b64…f968
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: 0xbb3f3cb7…74e046
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity