← previous blocknext block →recent activity
Analyzing
Block #100,917,834
25 transactions · 23 stateful · 2026-09-01 02:02:53 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,917,834 · 25 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
5w06w17w09w110w212w313w414w521w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62b937eb…c75c
0x34b655…2a6f
12 touches
15 conflicts
0xdc9915b5…542c
0x34b655…2a6f
10 touches
10 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x327c57dd…836d
0x34b655…2a6f
4 touches
1 conflict
0x3be13b22…e859
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
15 conflicts on slot 0x62b937eb63…22c75c
Audit this contract →
← previous block·next block →recent activity