← previous blocknext block →recent activity
Analyzing
Block #100,917,318
24 transactions · 24 stateful · 2026-09-01 02:00:18 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,917,318 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w18w211w012w114w315w317w420w121w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce39f2b1…4654
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc9915b5…542c
0x34b655…2a6f
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
6 touches
3 conflicts
0x451e482b…7e7d
0x34b655…2a6f
6 touches
3 conflicts
0x390c3915…570c
0x34b655…2a6f
4 touches
1 conflict
0x399d9048…6ef9
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
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 0xce39f2b144…404654
Audit this contract →
← previous block·next block →recent activity