← previous blocknext block →recent activity
Analyzing
Block #108,655,596
25 transactions · 23 stateful · 2026-09-28 04:26:51 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,655,596 · 25 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
1w02w03w14w05w18w09w115w016w120w021w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f4a79c6…45dc
0xd32edf…ff58
9 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x96309dab…a309
0x065c9d…c394
4 touches
1 conflict
0xa574b138…ca57
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x6f4a79c647…e145dc
Audit this contract →
← previous block·next block →recent activity