← previous blocknext block →recent activity
Analyzing
Block #100,153,614
17 transactions · 17 stateful · 2026-08-29 09:53:52 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,153,614 · 17 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
5w08w09w110w212w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1de7433…7339
0x8964d7…10f8
6 touches
3 conflicts
0xe1de7433…733d
0x8964d7…10f8
6 touches
3 conflicts
0xe1de7433…733e
0x8964d7…10f8
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x24afde28…4b92
0x8964d7…10f8
6 touches
3 conflicts
0xe1de7433…7338
0x8964d7…10f8
6 touches
3 conflicts
0xe1de7433…733c
0x8964d7…10f8
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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 0xe1de74338d…737339
Audit this contract →
← previous block·next block →recent activity