← previous blocknext block →recent activity
Analyzing
Block #100,922,486
32 transactions · 26 stateful · 2026-09-01 02:26:17 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,922,486 · 32 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
1w02w13w24w35w46w27w38w416w119w320w026w131w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x356b5f2e…e08a
0xd32edf…ff58
11 touches
15 conflicts
0x75a161d3…1890
0x065c9d…c394
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfac61869…a560
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
15 conflicts on slot 0x356b5f2e7c…94e08a
Audit this contract →
← previous block·next block →recent activity