← previous blocknext block →recent activity
Analyzing
Block #98,941,390
19 transactions · 19 stateful · 2026-08-25 03:51:44 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,941,390 · 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
1w02w13w05w06w08w19w010w211w212w313w414w315w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x3439deb5…2fa4
0x40c49f…2af0
8 touches
6 conflicts
0xd08db6ee…a943
0x40c49f…2af0
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x07a783d6…75ec
0x40c49f…2af0
5 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a06
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity