← previous blocknext block →recent activity
Analyzing
Block #100,578,302
20 transactions · 17 stateful · 2026-08-30 21:34:32 UTC
Parallelism
80/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,578,302 · 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
1w02w16w07w013w114w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d3c6659…4467
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0x53e67340…60f7
0x754704…b603
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 0x5d3c6659ba…b94467
Audit this contract →
← previous block·next block →recent activity