← previous blocknext block →recent activity
Analyzing
Block #100,133,224
30 transactions · 26 stateful · 2026-08-29 08:11:04 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,133,224 · 30 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
1w02w03w15w08w113w214w318w020w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x241ff48f…8534
0xd32edf…ff58
5 touches
3 conflicts
0x627738d1…db02
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x4e5afb3a…a338
0x3bd359…433a
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x59e52fc8…1566
0x754704…b603
4 touches
1 conflict
0xff53b6b2…2f57
0x754704…b603
4 touches
1 conflict
0x78863801…78d3
0xba1333…9ba9
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
3 conflicts on slot 0x241ff48f04…0e8534
Audit this contract →
← previous block·next block →recent activity