← previous blocknext block →recent activity
Analyzing
Block #108,684,817
29 transactions · 25 stateful · 2026-09-28 06:54:04 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,684,817 · 29 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
1w02w13w24w35w46w57w612w620w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x371cfb68…d868
0xd32edf…ff58
13 touches
21 conflicts
0x0e0c66fe…796f
0x1e2721…7805
6 touches
3 conflicts
0x93a8374e…896e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x431fa96d…6ac0
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0x1e2721…7805
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0051
0x1b6862…e19c
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
21 conflicts on slot 0x371cfb68f1…cfd868
Audit this contract →
← previous block·next block →recent activity