← previous blocknext block →recent activity
Analyzing
Block #98,675,246
23 transactions · 22 stateful · 2026-08-24 05:28:32 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,675,246 · 23 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
1w02w14w25w36w011w014w215w317w119w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaf3ec36…f7e4
0x40c49f…2af0
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x81932ded…6946
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: 0x40c49f17…d22af0
3 conflicts on slot 0xcaf3ec362b…31f7e4
Audit this contract →
← previous block·next block →recent activity