← previous blocknext block →recent activity
Analyzing
Block #100,923,503
18 transactions · 16 stateful · 2026-09-01 02:31:24 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,923,503 · 18 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
1w02w03w04w07w18w29w010w111w012w313w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4557124d…0715
0x34b655…2a6f
6 touches
3 conflicts
0x74dfcdee…66ea
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdc9915b5…542c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x71fad9ce…c11f
0x34b655…2a6f
4 touches
1 conflict
0xa46987d9…efd1
0x065c9d…c394
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 0x4557124d9f…d90715
Audit this contract →
← previous block·next block →recent activity