← previous blocknext block →recent activity
Analyzing
Block #100,568,011
15 transactions · 14 stateful · 2026-08-30 20:42:46 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,568,011 · 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
2w05w07w08w19w010w111w213w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f84ef84…787f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6d8ad688…4bf5
0xa6afd3…d132
4 touches
1 conflict
0x7c61fbae…d54c
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x96ed54e2…04ed
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 0x6f84ef84f8…d8787f
Audit this contract →
← previous block·next block →recent activity