← previous blocknext block →recent activity
Analyzing
Block #100,126,823
21 transactions · 20 stateful · 2026-08-29 07:38:51 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,126,823 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w110w211w313w414w315w116w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa165a261…b30d
0x34b655…2a6f
8 touches
6 conflicts
0x2cfe7c05…2b42
0x34b655…2a6f
6 touches
3 conflicts
0x50c61506…343f
0x34b655…2a6f
6 touches
3 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7b55ed0a…aed9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0xa165a26119…5bb30d
Audit this contract →
← previous block·next block →recent activity