← previous blocknext block →recent activity
Analyzing
Block #100,025,756
14 transactions · 13 stateful · 2026-08-28 23:10:02 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,025,756 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w48w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6c5ccf5…f208
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0xcf105918…3666
0x0555e3…2b9c
2 touches
0 conflicts
0x3a717ea1…51e7
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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
10 conflicts on slot 0xe6c5ccf5dc…46f208
Audit this contract →
← previous block·next block →recent activity