← previous blocknext block →recent activity
Analyzing
Block #108,646,470
25 transactions · 21 stateful · 2026-09-28 03:40:55 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,646,470 · 25 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
2w07w010w112w013w215w016w118w119w120w021w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5783e193…e58e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x3b6f4be8…ae66
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e5
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
0x34b655…2a6f
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
6 conflicts on slot 0x5783e1934c…bee58e
Audit this contract →
← previous block·next block →recent activity