← previous blocknext block →recent activity
Analyzing
Block #99,780,238
26 transactions · 20 stateful · 2026-08-28 02:31:13 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,780,238 · 26 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
2w03w15w28w010w111w212w314w415w517w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0xcb21158b…f18d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf11f7692…bb7b
0x34b655…2a6f
4 touches
1 conflict
0xf550fa1e…fa0e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
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: 0xf5b5f7f8…a36d70
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity