← previous blocknext block →recent activity
Analyzing
Block #106,004,608
40 transactions · 30 stateful · 2026-09-18 22:00:16 UTC
Parallelism
88/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,004,608 · 40 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
1w02w03w04w17w08w114w016w117w118w219w120w022w130w231w332w233w336w438w439w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x214f87c0…9db8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1b60b708…5b4b
0x34ae4d…3fc5
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x3f152ba8…cea6
0x34b655…2a6f
4 touches
1 conflict
0x7fec4dea…6005
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: USDC (USDC)
6 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity