← previous blocknext block →recent activity
Analyzing
Block #100,735,752
15 transactions · 15 stateful · 2026-08-31 10:46:34 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,735,752 · 15 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
1w05w06w17w212w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51dc
0x69a5f9…2fef
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
2 touches
0 conflicts
0x6d1ccb53…6db8
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: 0x35a73bac…1d6042
3 conflicts on slot 0x0000000000…000036
Audit this contract →
← previous block·next block →recent activity