← previous blocknext block →recent activity
Analyzing
Block #108,501,732
34 transactions · 23 stateful · 2026-09-27 15:32:02 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,501,732 · 34 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
1w03w112w013w214w215w122w124w225w326w427w530w232w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x384d4542…7896
0xd32edf…ff58
15 touches
28 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaa16b4d8…9321
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
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
28 conflicts on slot 0x384d45420d…ab7896
Audit this contract →
← previous block·next block →recent activity