← previous blocknext block →recent activity
Analyzing
Block #103,041,381
31 transactions · 27 stateful · 2026-09-08 12:38:22 UTC
Parallelism
87/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #103,041,381 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w213w118w219w324w025w126w228w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b5afdfb…083e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe5060fe3…ebea
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
6 conflicts on slot 0x6b5afdfbf8…0f083e
Audit this contract →
← previous block·next block →recent activity