← previous blocknext block →recent activity
Analyzing
Block #108,676,142
30 transactions · 25 stateful · 2026-09-28 06:10:19 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,676,142 · 30 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
1w02w18w210w011w012w117w122w223w024w125w227w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c8
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9ca
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9cb
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9ce
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9d0
0x508254…98bd
6 touches
3 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity