← previous blocknext block →recent activity
Analyzing
Block #100,147,299
25 transactions · 20 stateful · 2026-08-29 09:22:04 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,147,299 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5195946…0066
0xd32edf…ff58
15 touches
28 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c4
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
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
28 conflicts on slot 0xf5195946cf…370066
Audit this contract →
← previous block·next block →recent activity