← previous blocknext block →recent activity
Analyzing
Block #100,616,549
24 transactions · 23 stateful · 2026-08-31 00:46:57 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,616,549 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w09w010w111w212w113w314w418w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x633be797…3403
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x17d75238…7d7c
0x34b655…2a6f
6 touches
3 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0xc125f6c9…07f6
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
10 conflicts on slot 0x633be79768…c83403
Audit this contract →
← previous block·next block →recent activity