← previous blocknext block →recent activity
Analyzing
Block #100,160,386
10 transactions · 10 stateful · 2026-08-29 10:27:58 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,160,386 · 10 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a66a2b7…8e39
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e3c
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e3d
0x8964d7…10f8
6 touches
3 conflicts
0x7a66a2b7…8e3e
0x8964d7…10f8
6 touches
3 conflicts
0xa02175ba…c0ef
0x8964d7…10f8
6 touches
3 conflicts
0xa02175ba…c0f0
0x8964d7…10f8
6 touches
3 conflicts
0xa02175ba…c0f2
0x8964d7…10f8
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x7a66a2b727…378e39
Audit this contract →
← previous block·next block →recent activity