← previous blocknext block →recent activity
Analyzing
Block #108,969,641
24 transactions · 21 stateful · 2026-09-29 06:52:08 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,969,641 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w012w014w115w118w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae974d33…f023
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd2ac92ae…68fc
0x754704…b603
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
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 0xae974d3305…84f023
Audit this contract →
← previous block·next block →recent activity