← previous blocknext block →recent activity
Analyzing
Block #99,163,902
11 transactions · 11 stateful · 2026-08-25 22:37:58 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,163,902 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a4bb2c…f2c7
0x0eb88f…c0cc
6 touches
3 conflicts
0x388d69c4…4288
0x188d58…ea8e
6 touches
3 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
6 touches
3 conflicts
0xd9a7cef1…1ed5
0x188d58…ea8e
6 touches
3 conflicts
0xd06cc746…27e4
0x5ef52d…4343
6 touches
3 conflicts
0x38aa1898…fdf5
0x3bd359…433a
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd18a8dca…452b
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: 0x0eb88f97…8cc0cc
3 conflicts on slot 0xa5a4bb2c2d…50f2c7
Audit this contract →
← previous block·next block →recent activity