← previous blocknext block →recent activity
Analyzing
Block #100,922,909
17 transactions · 15 stateful · 2026-09-01 02:28:25 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,922,909 · 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
2w04w07w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x227dec47…fce5
0x34b655…2a6f
6 touches
3 conflicts
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
2 touches
0 conflicts
0x207ad3a3…f727
0x34b655…2a6f
2 touches
0 conflicts
0x2827ae77…4368
0x34b655…2a6f
2 touches
0 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: Perpl
3 conflicts on slot 0x227dec477b…49fce5
Audit this contract →
← previous block·next block →recent activity