← previous blocknext block →recent activity
Analyzing
Block #100,620,160
29 transactions · 19 stateful · 2026-08-31 01:05:06 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,620,160 · 29 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
1w02w13w27w38w410w011w012w115w528w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c0ea1b3…3d31
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xdb95e18e…c73e
0x1b6862…e19c
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
15 conflicts on slot 0x4c0ea1b32f…7b3d31
Audit this contract →
← previous block·next block →recent activity