← previous blocknext block →recent activity
Analyzing
Block #100,705,221
27 transactions · 23 stateful · 2026-08-31 08:12:58 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,705,221 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w413w415w616w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb1ec863…ab1b
0xd32edf…ff58
13 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x0a85a226…83bb
0x1b6862…e19c
8 touches
6 conflicts
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 0xdb1ec863c5…afab1b
Audit this contract →
← previous block·next block →recent activity