← previous blocknext block →recent activity
Analyzing
Block #100,151,403
9 transactions · 9 stateful · 2026-08-29 09:42:44 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,151,403 · 9 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x134c783f…c245
0x8964d7…10f8
6 touches
3 conflicts
0x134c783f…c246
0x8964d7…10f8
6 touches
3 conflicts
0x134c783f…c248
0x8964d7…10f8
6 touches
3 conflicts
0x9544ec59…6a31
0x8964d7…10f8
6 touches
3 conflicts
0x9544ec59…6a32
0x8964d7…10f8
6 touches
3 conflicts
0x9544ec59…6a35
0x8964d7…10f8
6 touches
3 conflicts
0x9544ec59…6a36
0x8964d7…10f8
6 touches
3 conflicts
0x9544ec59…6a38
0x8964d7…10f8
6 touches
3 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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x134c783f4b…a1c245
Audit this contract →
← previous block·next block →recent activity