← previous blocknext block →recent activity
Analyzing
Block #72,100,358
19 transactions · 17 stateful · 2026-05-03 05:43:50 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,100,358 · 19 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
2w03w04w15w16w28w110w014w115w216w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79c65b09…2894
0xd32edf…ff58
9 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
8 touches
6 conflicts
0x41cc0357…dc69
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x60bb42…87ea
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 0x79c65b0950…7e2894
Audit this contract →
← previous block·next block →recent activity