← previous blocknext block →recent activity
Analyzing
Block #100,923,162
17 transactions · 16 stateful · 2026-09-01 02:29:41 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,923,162 · 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
1w04w06w19w110w211w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x4e87305d…6648
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x54c47a12…8474
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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: Perpl
3 conflicts on slot 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity