← previous blocknext block →recent activity
Analyzing
Block #98,456,499
15 transactions · 15 stateful · 2026-08-23 10:35:51 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,456,499 · 15 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
1w02w03w17w18w29w310w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xc4d98fb1…c354
0x40c49f…2af0
6 touches
3 conflicts
0xefa45e1b…0ce3
0x40c49f…2af0
4 touches
1 conflict
0x13f91d60…4d86
0x40c49f…2af0
4 touches
1 conflict
0x1f70c82f…eea6
0x40c49f…2af0
4 touches
1 conflict
0x97e6bb3b…d0df
0x40c49f…2af0
4 touches
1 conflict
0xdc9526ab…def7
0x40c49f…2af0
4 touches
1 conflict
0xdf10cf3a…887c
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity