← previous blocknext block →recent activity
Analyzing
Block #98,538,073
42 transactions · 30 stateful · 2026-08-23 17:33:42 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,538,073 · 42 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
3w04w16w09w010w211w012w113w217w221w322w024w025w127w133w034w136w037w138w439w241w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x930f0898…f45c
0xd32edf…ff58
5 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x12c76c6b…9e93
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0xec2e5c34…46de
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: Perpl
3 conflicts on slot 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity