← previous blocknext block →recent activity
Analyzing
Block #100,791,100
20 transactions · 17 stateful · 2026-08-31 15:25:10 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,791,100 · 20 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
1w04w05w06w112w013w114w115w216w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x55192654…91fe
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0x54c6fb44…369a
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x4e87305d…6648
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity