← previous blocknext block →recent activity
Analyzing
Block #99,307,868
20 transactions · 17 stateful · 2026-08-26 10:42:19 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,307,868 · 20 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
1w03w14w15w07w18w29w010w111w012w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf549a705…e42d
0x065c9d…c394
3 touches
1 conflict
0xa09fdabc…8c1f
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity