← previous blocknext block →recent activity
Analyzing
Block #106,419,846
11 transactions · 11 stateful · 2026-09-20 08:50:03 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,419,846 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0x8401a9f1…e868
0x754704…b603
4 touches
1 conflict
0x363d5ac3…a29d
0x99c7a7…8bf0
4 touches
1 conflict
0x628e0d85…2e5c
0x99c7a7…8bf0
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x310a7246…2dcb
0x34b655…2a6f
2 touches
0 conflicts
0x5a6ef6e7…6125
0x34b655…2a6f
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: USDC (USDC)
1 conflict on slot 0x5a7e4e988c…d81f3b
Audit this contract →
← previous block·next block →recent activity