← previous blocknext block →recent activity
Analyzing
Block #99,187,518
20 transactions · 19 stateful · 2026-08-26 00:36:46 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,187,518 · 20 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
1w02w13w24w25w36w08w19w210w211w413w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x2274142b…f885
0x851145…3f07
8 touches
6 conflicts
0x7ea2bdd4…b4b0
0x851145…3f07
8 touches
6 conflicts
0x8b98c194…d69e
0x851145…3f07
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x371eea11…331e
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
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: 0x851145ea…9f3f07
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity