← previous blocknext block →recent activity
Analyzing
Block #102,428,653
30 transactions · 24 stateful · 2026-09-06 09:04:12 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,428,653 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w08w09w110w211w314w416w320w521w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0fd62c7…8609
0xd32edf…ff58
11 touches
15 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xca63dcd7…ca8b
0x065c9d…c394
5 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
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
15 conflicts on slot 0xf0fd62c79d…a28609
Audit this contract →
← previous block·next block →recent activity