← previous blocknext block →recent activity
Analyzing
Block #105,366,186
20 transactions · 19 stateful · 2026-09-16 16:24:30 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,366,186 · 20 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
2w03w06w17w08w110w111w012w113w214w316w118w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x41ac12b4…42ed
0x34b655…2a6f
6 touches
3 conflicts
0xb5dac821…b68b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x7c93b38a…9e69
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 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity