← previous blocknext block →recent activity
Analyzing
Block #100,792,242
25 transactions · 21 stateful · 2026-08-31 15:30:55 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,792,242 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w08w110w111w012w114w215w016w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd499502…53c6
0xd32edf…ff58
5 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0xfb7b36bf…38db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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 0xcd4995029d…3653c6
Audit this contract →
← previous block·next block →recent activity