← previous blocknext block →recent activity
Analyzing
Block #106,453,354
24 transactions · 20 stateful · 2026-09-20 11:38:45 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,453,354 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w110w011w113w216w018w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xfd3d8226…d72f
0x34b655…2a6f
4 touches
1 conflict
0xfd3d8226…d730
0x34b655…2a6f
4 touches
1 conflict
0x626418b6…20b6
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x456d845e…913c
0x065c9d…c394
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: USDC (USDC)
3 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity