← previous blocknext block →recent activity
Analyzing
Block #100,893,496
23 transactions · 22 stateful · 2026-09-01 00:00:28 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,893,496 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w110w212w115w116w217w219w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6137e5ce…c5fa
0xd32edf…ff58
5 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0922e0c0…6e38
0x34b655…2a6f
4 touches
1 conflict
0x0922e0c0…6e39
0x34b655…2a6f
4 touches
1 conflict
0x2a6c7002…ba26
0x34b655…2a6f
4 touches
1 conflict
0x2cc1dbc9…bdd2
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity