← previous blocknext block →recent activity
Analyzing
Block #108,713,217
32 transactions · 19 stateful · 2026-09-28 09:17:14 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,713,217 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w010w111w120w021w222w323w425w426w127w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01bd4c51…74d6
0xd32edf…ff58
9 touches
10 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x65f60d9b…95b5
0x065c9d…c394
3 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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x01bd4c519b…9c74d6
Audit this contract →
← previous block·next block →recent activity