← previous blocknext block →recent activity
Analyzing
Block #100,566,710
26 transactions · 23 stateful · 2026-08-30 20:36:13 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,566,710 · 26 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
3w05w06w18w011w012w113w214w115w016w117w218w119w220w121w322w223w425w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x55010ec8…ea31
0x34b655…2a6f
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2202504e…fad0
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity